Stabilizing Performance with Query Store
summary
Shows how Query Store lets DBAs stop regressions without code changes by using plan forcing, automatic plan correction and Query Store Hints. Demo on WideWorldImporters isolates one statement that alternates between plans producing ~690 logical reads / 841 ms and a bad run with ~55,000 reads (26,000 matching rows), demonstrating extreme plan sensitivity. Includes T‑SQL to force or auto‑correct plans, notes default per‑statement plan cap (200), and publishes demo scripts on GitHub; treats forcing as a temporary fix pending code/schema changes.
AI-written summary · about
chapters (5)
- 0:00Introduction and roadmap
- 2:22Challenges in query planning
- 6:27Performance troubleshooting
- 9:48Demonstration setup and analysis
- 15:30Using Query Store insights
related talks
19mStabilizing Performance with Query Store
19mStabilizing Performance with Query Store
22mA Beginners guide to Query Store
20mElevating SQL Server Performance with Query Store Hints
53mBanishing Slow Queries with Intelligent Query Processing
48mQuery Store: A Retrospective
49mPerformance Features in SQL Server and Azure SQL
44mImproving Performance with Intelligent Query Processing
