The Data IO % alert notifies you when its configured condition is met on Azure SQL Database instances so you can investigate and respond.
Mini DBA describes this alert as: % of Data IO used by this database Sustained high usage may indicate poor T-SQL or index design or a need to upgrade service tier Mini DBA evaluates this alert once a minute so changes are detected quickly. Because duration is used, Mini DBA can avoid treating a single short spike as a full incident when the condition clears quickly.
This alert helps reveal query and workload pressure. It points you toward expensive statements, plan changes, inefficient access patterns, or bursts of work that need investigation before they affect service levels.
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: % Data IO. Major threshold: 95 %. Minor threshold: 85 %. Comparison direction: over. Duration is used, so prefer requiring the condition to persist before paging people for transient spikes. For an over-threshold alert, decreasing a threshold makes that severity fire sooner; increasing it tolerates more load or pressure. Set the minor threshold as an early-warning level and the major threshold at the highest acceptable value for the service.
Use the query, wait, and performance views to find the statement or subsystem behind the pressure. Compare against the recent baseline, update statistics, tune indexes, adjust application batching, and move maintenance work away from peak periods where possible.
If this alert is noisy, check whether the workload naturally has short bursts. Raise the duration or threshold for expected batch windows, but keep a lower route for production systems where user-facing latency matters. Avoid simply disabling the alert until you know whether the noise is caused by threshold choice or by a real capacity trend.