Use the Error Log Medium Severity 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: Errors in the Sql Server error log of severity 15 or 16 These levels of severity covers user correctable errors such as problems with High Availability Groups or queries that throw errors The default evaluation frequency is Minute, so the alert is intended to be close enough to operational reality for live triage.
This alert gives Mini DBA a focused signal for a condition that can affect SQL Server reliability, performance, or operational visibility. It helps the team move from a general problem report to a specific metric, threshold, and investigation path.
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.
This alert is not primarily driven by a numeric threshold in Mini DBA. Tune the schedule, scope, severity, and notification route so that the alert matches the importance of the instance. 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.
Free space by removing safe-to-delete files, expanding the volume or tablespace, moving growth-heavy objects, correcting retention settings, or shrinking only after a documented one-off event. For recovery-related areas, verify that backups and log shipping or archiving are healthy before deleting anything.
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.