Use the Azure Storage Mb alert in Mini DBA to monitor Azure SQL Database instances and make this condition visible before it becomes a wider database incident.
Mini DBA describes this alert as: Azure Storage Mb The MaxThreshold represents the amount of Mb usage that will trigger the alarm
This alert gives Mini DBA a focused signal for a condition that can affect Azure SQL Database 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 on any monitored Azure SQL Database instance where this condition would require an administrator to investigate or communicate with the application team. Tune noisy development systems after you have a short baseline.
Threshold meaning: Mb used. Major threshold: 50000 Mb. 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.
If the alert creates repeated noise, review whether it is enabled on the correct instances, whether maintenance windows are configured, and whether the minor and major routes match the real business impact. Keep enough history to prove the new setting before changing it broadly.