Database Health Monitor

Is Your SQL Server Security Score Hiding a Critical Fail?

A flat SQL Server security score hides the one failure that matters. See how weighting by severity puts the critical findings first.

SQL Server connections by database turns a baffling instance total into a named application, with pool limits, leaks and master slices explained.

When the instance connection total jumps, SQL Server connections by database shows which application is holding them. Here is how to read the split.

Vendor installers leave behind SQL logins with CHECK_POLICY off, which means no complexity, no expiry and no lockout. Here is why they survive every review,… Read More »The SQL Login Nobody Remembers: Finding Accounts With the Password Policy Turned Off

Is your master database size normal? Read the object count first, then the used and free split in each file, and only then the file… Read More »Master Database Size: Read This Row Before the Megabytes

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

Open an SSRS shared dataset report and the biggest number is the wrong place to look. Here is the order that finds broken reports and… Read More »SSRS Shared Dataset Report: What to Read First

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?

Is a SQL Server query slow when busy because of its plan or because of its neighbors? Compare quiet and busy Query Store intervals to… Read More »SQL Server Query Slow When Busy? Find Out Which Kind

A deadlock heat map shows which hour and day your SQL Server deadlocks cluster, so you can find the colliding job instead of guessing from… Read More »Deadlock Heat Map: Find the Hour Your Deadlocks Hit