Azure SQL Database blocked processes alert


The Blocked Processes alert notifies you when its configured condition is met on Azure SQL Database instances so you can investigate and respond.

Screenshot pending: Mini DBA Azure SQL Database Blocked Processes alert screenshot placeholder

Alert summary

  • Platform: Azure SQL Database
  • Alert category: Query
  • Default enabled: true
  • Default evaluation frequency: Minute
  • Threshold label: Blocked spid
  • Unit: sessions

What Mini DBA checks

Mini DBA describes this alert as: Processes being blocked by other processes A degree of this is to be expected in busy environments as locks are taken out on objects The MaxThreshold represents the number of blocking processes that it takes to trigger an alert 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.

How this alert helps

This alert highlights concurrency pressure. Blocking, long sessions, and lock waits can turn a healthy server into a slow user experience, so the alert gives administrators an early route to the sessions, statements, and applications involved.

When to enable it

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 guidance

Threshold meaning: Blocked spid. Major threshold: 5 sessions. Minor threshold: 0 sessions. 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.

Remediation for an active alert

Open the activity, blocking, and query views to identify the lead blocker, SQL text, wait type, login, host, and application. Prefer fixing the query or transaction pattern, but kill or cancel the blocking session when the business impact is higher than the rollback risk.

Investigation workflow

  1. Confirm the alert is still active and note the first seen time, affected instance, and severity.
  2. Review the lead session, SQL text, wait type, blocking chain, login, host, and application name in Mini DBA before changing configuration or ending sessions.
  3. Compare the current value with the normal baseline for the same time of day or maintenance window.
  4. Record the cause, corrective action, and whether thresholds or routing should be adjusted after the incident.

Avoiding alert noise

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.

Related pages