An oStress load test runs one query from many connections at once, so you can watch SQL Server under a crowd. This post explains the main switches and runs a small first test with five connections. It also builds the same test with sqlcmd workers, for machines without oStress.
Query Store Status for Every Database in SQL Server
Query Store status for every database takes two queries, and the first is not enough. This post builds four demo databases, shows why the is_query_store_on flag hides frozen and read-only states, and runs one script that reads the real state of each database. It also shows what Query Store costs in memory.
Forcing a Plan in Query Store and Checking That It Held
Use forcing a plan in Query Store with verified IDs, then audit force failures and runtime results every week so the fix stays useful.
Duplicate Statistics: Auto-Created Stats That Shadow Index Statistics
Find duplicate statistics on index-leading columns, compare freshness and sampling, and generate cautious DROP STATISTICS candidates.
Rebuild All Indexes on a Table in SQL Server: SSMS and T-SQL
To rebuild all indexes on a table, right-click the Indexes folder in SSMS and choose Rebuild All, or run ALTER INDEX ALL with REBUILD. This post checks fragmentation first, rebuilds a demo table and shows what the command does to a disabled index. It also compares REBUILD with REORGANIZE and the options that matter.
Query for CPU Pressure: Sample the Scheduler Queue
To sample the scheduler queue, read the runnable counts of every scheduler eight times, one second apart, and compare the result with a baseline. This post shows the queue on a quiet server and again while more busy sessions than schedulers run. It reads the spread, the streak and the average that tell pressure from noise.
Canceled Query Plan: Three Ways to Capture It in SQL Server
A canceled query plan can be captured with Live Query Statistics, with a live plan query while the statement runs, or from Query Store after the cancel. This post runs a long query, reads its plan while it runs, cancels it and then reads the aborted run from Query Store. It also explains which plan each method returns.