Skip to main content

An Introduction to SQL Server 2016 Query Store

By David Postlethwaite

David is delivering a talk An Introduction to SQL Server Query Store at SQL Saturday Iceland today - this post has been scheduled to coincide with his talk

If you are at SQL Saturday Iceland today go and see his session.

There will be a series of post with an introduction to SQL Server Query Store over the next few weeks. In this post at the bottom you will find a video of David's talk. Enjoy!

Let me start by asking you a question.

Have You Ever experienced system outage or degradation which you were expected to instantly fix?
You know the sort of thing where the database is responding slowly and the boss is standing over the top of you demanding you fix it.
He’s shouting “Get it fixed we’re losing customers and money.” But you can’t quickly see what’s going on

Have you ever been asked why a database slowed down this morning?
Why did it? What changed this morning.
And what changed since then to make it go back up to speed?

Have you ever upgraded an application to the latest SQL version and suffered performance issues?
Microsoft claim SQL 2016 is 30% faster so why has your database suddenly gone slow after you moved it to the shiny new server?

Have you ever released new code and suffered a slow down?
New code should run faster, right? But when you’ve released it to production its going slower and you can’t see why.

Have you ever experience unpredictable performance?
One minute its fast, the next minute is gone slow.

Have you ever wanted a way to track queries over time to see workload and workload patterns and changes from the baseline?

Have you ever wanted to be able to answer quickly questions like “Why has this query gone slow? What was the execution plan this morning compared to now? Why has it changed?”

Have you ever wanted to force SQL Server to use a different execution plan to the one it has now?
You’ve worked out SQL was using a different execution plan this morning. How can you make SQL use it this afternoon without rewriting code?
And keep it that way?

Then SQL Server 2016’s Query Store maybe the answer!

You can view a recording of David's talk here, its 50 minutes long:


Popular posts from this blog

SQL Server 2012 and Virtual Service Accounts

This post is written by David Postlethwaite
If you are using SQL Server 2012 you will probably have noticed that the default account for the SQL services has changed from that used in previous versions. With SQL 2005 and 2008 the default account for SQL service and SQL Agent service was “NT Authority\System”. This is one the built in accounts on a Windows machine, managed by the machine and selectable from a dedicated dropdown list

The Network Service account was introduced in Windows 2003 as an alternative to using the LocalSystem account, which has full local system privileges on the local machine, a major security concern.
The Network Service has limited local privileges easing these security concerns but when many services on a machine use the Network Service account it becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account.
Also, this account, by default, has sysadmin per…

Always Encrypted

By David Postlethwaite

Always Encrypted is new features in SQL Server 2016 and it is also available in Azure SQL Database. Here you can encrypt columns in a table with a master key and a certificate so that they will appear as encrypted strings to those who don’t have the required certificate installed on their pc.
Once the certificate is installed on the computer then the unencrypted data can then be seen as normal.

The data passes from database to your application as the encrypted value, only the application with the correct certificate can unencrypt the data so it is secure across the wire. This will go some way to resolving the concern of people worried about putting their sensitive data on a shared server in the cloud such as Microsoft Azure and accessing the data across the Internet.

At the time of writing Always Encrypted is only supported with ADO.NET 4.6, JDBC 6.0 and ODBC 13.1 but expect other driver to become available.

The calling application (including SSMS) must also hav…

New in SQL Server 2017: Graph Databases

David has recorded and published a video of his presentation on SQL Server Graph Database. In his video which you can watch below, David provides an excellent introduction into SQL Server 2017 Graph Databases. In his presentation he looks at Tennis results at tournaments for  his favourite player "The Fed"  Rodger Federer.

David  shows how to set up graph database and work with them in SQL Server 2017.

Graph Database is not new. Other vendors have had graph database capabilities for some time so Microsoft are quite late to the market. In David presentation it appears that Microsoft have done a reasonable job of implementing some of the graph database features but he does point some of the limitations of the Microsoft product too and suggests that it is not ready for production yet but Microsoft seem serious about this feature.

Please watch the video and feel free to leave a comment or feedback - David is delivering a version of this talk on Graph databases in SQL Saturday Ka…