A workshop question: what is the performance comparison of function TRIM and LTRIM(RTRIM) in SQL Server? Here are the test results.
Disk Space Needed to Build a Clustered Index on a Big Table
A clustered index build holds the old table and the new index at the same time. Here is a small demo of that peak, and what to check first.
Collecting Server Hardware Facts Before a Tuning Session
Capture server hardware facts from SQL Server views, keep an inventory, and distinguish visible resources from workload sizing evidence.
High CPU Consumption in SQL Server: Where to Look First
High CPU consumption in SQL Server comes from a handful of causes, and a short checklist finds them in order. This post reads the scheduler queue, ranks cached queries by CPU, and checks the Common Criteria Compliance setting that caused a known CPU problem after upgrades. It ends with the update that fixed that case and the questions to ask before you add cores.
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.
Automatic Plan Correction: Reading SQL Server’s Tuning Advice
Read automatic plan correction advice, compare regressed and recommended plans, and verify that forcing the last good plan held.
Sort in TempDB for Faster Index Rebuilds: When It Helps
To sort in tempdb during an index rebuild, add WITH (SORT_IN_TEMPDB = ON) to ALTER INDEX. This post tests the option and shows that the user database log stays the same size, because only the sort workspace moves. It also explains when the option helps, how much tempdb space it needs, and when to leave it off.