SQL in PE 06 September 2017 sponsored by Pragmatic Works and MIcrosoft

Registration

Welcome and Keynote by Deveraux Joubert and Jody Roberts

One of the new features announced for SQL Server 2017 is Adaptive Query Plans, query plans that can change after the query starts executing.

This session will show why this is a radical departure from the way that things have worked until now and how it can improve the performance of some query forms. We’ll look at the places where adaptive query plans work and compare the performance of queries using adaptive query plans to see just what kind of improvement it can make.

In this session we look at how R in SQL Server can be used in a production environment to automatically run models against data coming into SQL Server, as well as update the model with no interference from the data scientist.

Tea/Coffee Break

Master Data Services can be readily be employed for Rapid Application Development. We shall be looking at important development, data security and data maintenance aspects, all based upon a recent client implementation.

Lunch

In this session we will look at what and who to take in consideration when thinking about a data strategy

One of the hardest things to do in SQL is to identify the cause of a sudden degradation in performance. The DMVs don’t persist information over a restart of the instance and, unless there was already some query benchmarking (and there almost never is), answering the question of how the queries behaved last week needs a time machine. Up until now, that is. The addition of the QueryStore to SQL Server 2016 makes identifying and resolving performance regressions a breeze. In this session we’ll take a look at what the QueryStore is and how it works, before diving into a scenario where overall performance suddenly degraded, and we’ll see why QueryStore is the best new feature in SQL Server 2016, bar none.

SQL Server error handling is NOT easy. There are so many ways you can be tripped up! In this session we will look at where you can go wrong, as well as what to do and not to do. Among other things we will look at why XACT_ABORT can be the devils work!

Closing