Green in the dashboard does not mean safe to fail over. See how availability group lag turns into data loss and redo time, and where… Read More »Availability Group Lag: What a Failover Would Cost You
Task Manager says SQL Server ate all the RAM. Here is how to read SQL Server memory usage as three nested layers and find the… Read More »SQL Server Memory Usage: Where Did All the RAM Go?
Query Store stopped collecting, and nothing told you. Here is how to prove whether the history behind your tuning reports is really there, and fix… Read More »Query Store Stopped Collecting? How to Tell Fast
A deadlock count tells you there is a problem. SQL Server deadlock history grouped by object and statement pair tells you what to change. Here… Read More »SQL Server Deadlock History: Find What Collides
The SQL Server error log holds the evidence for your last outage. Here is how to read archives, group the noise, and spot 825 and… Read More »Reading the SQL Server Error Log Before It Reads You
ReportServer database size rarely grows from report definitions. See which tables, in the catalog and its temp database, actually reserve the space.
What is in master often surprises the team that has to rebuild it: credentials, triggers, and startup procedures nobody documented.
Most SQL Server maintenance window schedules are typed in once and never checked. Here is how to measure the quiet hours instead of guessing at… Read More »Your SQL Server Maintenance Window Is a Guess. Measure It
A management data warehouse can stop updating while its Agent jobs still show green. Here’s where SQL Server keeps the real failure text.
SQL Server index fragmentation percentage can be misleading. Here is the number that actually predicts what a rebuild will buy you, and where to find… Read More »SQL Server Index Fragmentation: Stop Chasing the Percent
