The Query Store captures a history of queries, execution plans, and runtime statistics, which persist within SQL Server and can be reviewed later.
Do you hate when someone wakes you up in the middle of the night and tells you that some query is slower and you need to investigate it? With SQL Server 2017 you might easily do this, or even let SQL Server do this job for you.
The query store gives us a novel way of identifying those queries that are causing performance problems when they are parameterized by SQL Server for reuse. Although it is relatively simple to ensure that certain troublesome queries avoid the problem, it is laborious to identify these queries. Additionally, Query Store gives us the means to fix the problem for groups of queries by means of plan guides without changing the DDL at all. Dennes Torres explains the details
Erin Stellato demonstrates how to use the new DBCC CLONEDATABASE feature, in combination with Query Store, to test index and query changes.
Once you have Query Store enabled on your databases, runtime statistics are generated for your queries; but what about the natively-compiled stored procedures and memory optimised tables that come with In-Memory OLTP? Do you get the full range of runtime statistics? This is an intriguing question that Enrico explores and answers.
When you force a query plan via the Query Store, you will need to track what happens: Sometimes the request to force a plan will fail, and you will want to know when and why. There are several ways of getting feedback, ranging from the built-in reports to using extended events. Enrico explains the details.
Article shows how R Services can help database administrators with their daily work
Arshad Ali demonstrates how you can analyze the data collected by Query Store either with T-SQL scripting or with the graphical user interface in SSMS.