1. Introducing the SQL Server 2016 Query Store
E. van de Laar

2. Thank you to our AWESOME sponsors!

3. About me Chief Consultant DotNine
Technical Consultant PinkRoccade Healthcare
MVP Data Platform
Blogger
Author
@evdlaar

4. Flight recorder or “black box”
Flight recorder or “black box”. The round part is the CSMU (Crash-survivable memory unit) Origin of black box seems to be because early versions were photograph based
© aerophotoworks.com

5. The flight recorder can record 25 hours of flight data and 2 hours of conversations
© aerophotoworks.com

6. Flight recorders are virtually indestructible
Flight recorders are virtually indestructible. The can survive an impact of 3400 g’s, an impact force of 3400 times its own weight and can survive for 30 days in salt water.
© Manny Ceneta

8. But today we aren’t going to talk about airplane flight recorders but the SQL Server flight recorder: Query Store!

9. Agenda What is this Query Store? Query Store Architecture
Analyzing data inside the Query Store
Plan forcing using the Query Store
Query Store performance considerations

10. What is this Query Store?

11. What is this Query Store?
New feature in SQL Server 2016
Captures and stores query information on a per-database level
Allows query performance analysis using built-in reports and DMVs
Retains query history
Integrated directly in the SQL Server Engine

12. What is this Query Store?
Why do I think this is one of the best features in SQL Server 2016?
Saves time (and money)
Makes performance tuning available for everyone*
Examples: CE older to new version, Testing software releases, etc

13. Query Store Architecture
Query plans and text are aggressively written to disk to persist them. All of the information on-disk is recorded in the new query store schema in the Primary Filegroup of the user-database.
Query Store DMVs and reports can access both the In-memory and on-disk storage.

14. [DEMO]
Demo: Enabling Query Store and Query Store configuration

15. Analyzing data inside the Query Store
Two* methods available to analyze the data inside the Query Store - Built-in reporting - DMVs
Built-in reporting provides additional, easy accessible, features like plan comparison and forcing
DMVs are great for programmatically accessing Query Store data

16. [DEMO]
Demo: Built-in reporting

17. Analyzing data inside the Query Store
DMV overview and relations

18. [DEMO]
Demo: DMVs

19. Plan forcing through the Query Store
Next to giving insight into the performance of your queries, we can use the Query Store to force a specific Execution Plan for a regressed query
[DEMO]
If you ever had to create a plan guide this new option will make your life a lot easier

20. Query Store performance considerations
Performance impact: 3-5% on average
Depends on: - Data Flush Interval setting - Amount of (unique) queries - Storage performance - General performance of the box - etc…
BUT…your mileage may vary

21. Query Store performance considerations
There are many ways we can monitor the Query Store - Perfmon - Wait Statistics - Extended Events
[DEMO]

22. Summary Query Store is an incredible powerful addition to SQL Server
It helps making analyzing query performance easier
Allows you to easily force Execution Plans*

23. Additional reading
Monitoring Performance By Using The Query Store (
Simple Talk: “The SQL Server Query Store” article series (

24. Additional reading
Query Store Dashboards (
sp_WhatsupQueryStore (