Compare a good and a bad plan in Query Store using runtime history, SSMS Compare Showplan, estimates, joins, grants, and parallelism.
Finding Regressed Queries in Query Store After a Deployment
Find regressed queries in Query Store using weighted before-and-after duration and CPU, then compare plans and changed procedure text.
ABORT_QUERY_EXECUTION: Stopping a Runaway Query With a Query Store Hint
ABORT_QUERY_EXECUTION is a SQL Server 2025 Query Store hint that makes one known bad query fail before it uses any CPU. This post sets the hint, shows the exact error the caller gets, lists and clears the hint, and covers the traps: exact text, SET options and queries already running.
Why Query Store Actual Operation Mode is Not Same as Requested? – Interview Question of the Week #248
Question: Why Query Store Actual Operation Mode is Not Same as Requested? Query Regression (poor performing queries, once working great)
Listing Databases Below the Server’s Native Compatibility Level
Find databases below the native compatibility level, generate reviewable ALTER statements, and prepare Query Store checks safely.
Finding the Plan That Changed: Query Store Plan History
Read Query Store plan history, compare duration by interval, find plan changes, and review a temporary force with an exit plan.
Query Store Read-Only: Size Limits That Stop Capture
Your Query Store may want READ_WRITE and still be READ_ONLY. Here is how it happens, how to read the reason, and how to get capture back.