Use the Maximum Connections 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: Maximum connections The number of concurrent client connections to the instance. This may indicate periods of very high use or inefficient client application code. The default evaluation frequency is Minute, so the alert is intended to be close enough to operational reality for live triage.
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: Connections. Major threshold: 4000 connections. Minor threshold: 2000 connections. 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.
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.