Force a plan with Query Store when a query turns slow after a plan change. This post builds a regression, finds both plans in Query Store, forces the good one, measures what forcing costs and shows when to unforce.
Assessing a Database Before a Migration
Assessing a database before a migration covers features in use, compatibility, size, dependencies, and the evidence needed before a date is promised.
Getting SQL Server Data Into Power BI
Power BI can read SQL Server through Import or DirectQuery; stable views, folding, and workload checks keep the database responsive.
Finding the Slowest Statement Inside a Stored Procedure
Find the slowest statement inside a stored procedure using query stats offsets, CPU and read totals, then confirm with Query Store.
Raising a Database Compatibility Level Safely
Raise a compatibility level safely by capturing a Query Store baseline, changing one database, comparing plans, and keeping a tested reversal.
Calculating the Cost of a Slow Query
Cost of a slow query includes frequency, CPU, reads, waits, and user time; learn to turn SQL Server measurements into a practical tuning priority.
Finding the Most Frequently Run Queries
Most frequently run queries can consume large SQL Server resources even when each call is fast; use plan cache and Query Store to find them.