I evaluate monitoring tools by collection cost, historical context and usefulness in choosing a correction. Customer discussions shaped those three criteria.
SQL SERVER – Reviewing Sleeping Sessions Before Terminating Any Session
An inactive or sleeping session may still be a useful pooled connection. A customer case prompted my earlier session-cleanup script.
Spotting Unusually Small Backups Against Each Database’s Average
Flag unusually small backups against database-specific history, use aggregate filtering, and investigate alerts without assuming data loss.
Runnable vs Suspended: What Each sp_who2 Status Means
Runnable vs suspended is the question I hear most about the sp_who2 status column. A Runnable session waits for CPU, and a Suspended one waits for a resource such as I/O. Here are all five statuses in plain words.
Tracking Backup Throughput and Duration From msdb History
Track backup throughput and duration from msdb history, compare recent trends, and keep striped devices from duplicating backup totals.
Right-Sizing SQL Server: Reading CPU and Memory Use Before Consolidation
Base right-sizing SQL Server on sampled CPU, memory pressure, buffer use and interval I/O, then compare peaks across a full business cycle.






