Use the Disk Queue Length alert in Mini DBA to monitor SQL Server instances and make this condition visible before it becomes a wider database incident.
Mini DBA describes this alert as: IO items waiting to be serviced by the disk High disk queue length can signify poor IO configuration. Check if multiple databases sharing the same drive. The thresholds are device dependant so experiment with the settings The default evaluation frequency is Minute, so the alert is intended to be close enough to operational reality for live triage.
This alert protects storage and recovery capacity. It helps you find growth, retention, and backup conditions that can stop writes, break recovery objectives, or leave the server without enough working space for normal database activity.
Enable it once the instance has a normal workload baseline. It is especially useful on busy OLTP, reporting, and integration systems where resource pressure can quickly become user-visible.
Threshold meaning: Queued items. Major threshold: 100 queued items. Minor threshold: 4 queued items. Comparison direction: "over". Use higher thresholds on batch-heavy, development, or intentionally bursty systems where brief pressure is expected. Use lower thresholds on latency-sensitive production systems, small instances with little headroom, and services with strict recovery or availability commitments.
Open the related Mini DBA page for the instance, compare the current value with the recent baseline, identify whether the change is caused by workload, configuration, host capacity, or maintenance, then record the corrective action in the incident notes.
Storage alerts should usually stay enabled even on quiet systems because the impact of missing them is high. Tune warning thresholds to leave enough time for approval, provisioning, and validation, especially when storage changes are handled by another infrastructure team.