Flag unusually small backups against database-specific history, use aggregate filtering, and investigate alerts without assuming data loss.
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.
SQL SERVER – 5061: FIX Error: ALTER DATABASE failed because a lock could not be placed on database ‘Database Name’. Try again later.
Trying to take a test database offline, we hit Msg 5061: ALTER DATABASE failed because a lock could not be placed on database. Here is how to fix it.
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.
Detect Performance Problems in SQL Server With DMVs
To detect performance problems in SQL Server, start with four suspects and a few dynamic management views that show CPU waits, memory use and the system_health session. This guest post by Eduardo Castro explains where to look first.
Reading the system_health File Target With Plain T-SQL
Locate the system_health file target, read its retained events with T-SQL, and inspect serious errors, connectivity records and waits.
A Performance Counter Baseline Saved to a Table Every 15 Minutes
Save a performance counter baseline every 15 minutes, calculate interval rates, detect resets, and compare a defined week with last month.