The performance of a Dynamics NAV installation can be much impacted by the setup and configuration of the SQL Server database storing data. The MSDN documentation of this topic has been improved a lot during the last year, hoping that better database performance will give better response times and therefore also improve end user satisfaction. In this session, I will go into details around installation and configuration of SQL Server with a focus on why different practices are recommended and how these recommendations will help you get an optimized database experience for Dynamics NAV.

You can learn SQL in three days but it'll take you 10 years to become good at it. In this session we will have a look at some basic design errors and get a notion of the things that absolutely doesn't work. Antipatterns is a way of naming common design errors in order to make them easier to remember - even if you haven't done them yet. We will become acquainted with antipatterns on a physical level, a logical level and an sql-queries and application level, and spice it up with some seriously foolish errors made by me and my colleagues. The session is relevant for developers and DBAs.

SQL is based on the relational  algebra, right? Relational algebra is based on set theory, right? So we would expect SQL to  kind-of respect common sense from set theory. Like A union A has the same number of elements as A. Well, this is not always the case with SQL. 

​

Come and have fun when we explore scenarios of simple SQL statements, where I guarantee you moments of inner WTF. 

In many data warehouses we model fact tables with measures based on attributes which we can count and do arithmetic upon. It is more difficult to handle fact tables with measures based on length of intervals of events happening in the source systems. So questions like "What are the typical waiting times in our order process?" are seldomly modelled in the data warehouse. Especially if the event data comes from different source systems. In this talk I will show you different techniques and models related to time: process mining, lean, six sigma, process datawarehousing, relational temporal theory and SQL 2016 temporal.

​Using a health care case story, we will develop a common data warehouse architecture with staging, Enterprise Data Warehouse (EDW) and datamart layers. We will touch upon concepts and patterns like stage copy/stage history, surrogate/business keys, dimensional modelling, inferred members, data warehouse history types 1/2, datamarts and many more. Concepts/patterns are introduced from problems from the case. The talk has equal focus to the “whys” as well as the “hows” in data warehousing.

The product Effektor was (and still is being) developed using Scrum over sprint more than 80 sprints. During this time, we realized that we needed to have more written practices on requirements and design than just epics and PBI descriptions. Come and hear about how we combined the scrum process with feature descriptions, requirement specifications and design documents – methods that you might connect with more waterfally development practices.

My thesis in the Master of IT management program was about the life of IT operations people and how they learn. Specifically I worked on the following three research questions:

1. What is the difference between a normal IT operations professional and a true expert

2. How can you make your IT operations professionals better

3. What can you do to make your experts thrive

Come and hear about my results and how to make your IT operations professionals grow

Want to start a new business? You have the great idea, but what about creating a business plan, web site, invoicing, CRM, social media and all the other infrastructure you need to operate that great startup. Come and spend an hour with me and see how we did it with our new company Effektor. Ask all the questions you have. I might even be able to answer them.