A Beginners guide to Query Store
summary
Query Store captures and retains execution plans and runtime telemetry per database so regressions are visible over time, storing estimated plans, runtime stats and wait statistics and letting you force a plan when one plan outperforms alternatives. Enable it with ALTER DATABASE SET QUERY_STORE = ON and set operational_mode=READ_WRITE; defaults flush to disk every 90 seconds and aggregate every hour (adjustable). UI reports surface regressed queries, top resource consumers and forced-plan usage; reduce capture intervals for fast incident troubleshooting at the cost of more storage.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:38Query store overview
- 6:27Plan cache vs query store
- 10:00Plan types and data capture
- 12:57Forcing plans and stats
- 17:20Troubleshooting with weights
- 20:06Conclusion and resources
related talks
22mA Beginners guide to Query Store
48mQuery Store: A Retrospective
19mStabilizing Performance with Query Store
51mMaking the SQL Query Processor Work for you
20mElevating SQL Server Performance with Query Store Hints
26mUsing Azure Query Store to Understand PostgreSQL Performance
50mQuery Store Best Practices- 50mQuery Store Best Practices