Azure SQL Database Alerts shows alerts associated with an individual Azure SQL database. Use it for focused database-level triage.
Workflow
- Open the Azure SQL database.
- Select Alerts.
- Review severity, message, and time.
- Open related pages such as Activity, Waits, Files, Elastic Pools, or Health Checks.
- Use Configure and Copy Config to edit or copy database alert policy.
- Use global Alerts for estate-level alert review.
How To Use Azure SQL Database Alerts
Azure SQL Database Alerts focuses on one database, which is useful when a single tenant, application, or workload is affected. Start with alerts that are high severity, new, repeating, or close to the time users reported a problem. Then open the related monitoring page to confirm the evidence behind the alert.
An alert about activity or blocking should be investigated with Azure SQL Activity, Azure SQL Locks, or Azure SQL Deadlocks. A performance alert should be compared with Azure SQL Queries, Azure SQL Query Store, and Azure SQL Waits. Capacity alerts often need Azure SQL Database Summary, Azure SQL Files, or Azure SQL Elastic Pools.
For operational review, record the alert, database, time, owner, and outcome. Repeating alerts should either lead to a fix or a deliberate threshold decision.
Use Copy, Export, And Import Alert Configuration to copy alert configuration between Azure SQL databases of the same operational role. Azure SQL logical server alert pages are roll-ups, so copy configuration from the individual database or elastic pool alert page.
Azure SQL Database Alert FAQ
Why do database alerts also appear globally?
This page focuses on one database. Global Alerts helps prioritize alerts across all engines and customers.
What if an alert fires during normal workload?
Compare it with historical behavior, scheduled jobs, and elastic pool pressure before changing thresholds.
Who should receive Azure SQL alerts?
Use Alert recipients and recipient groups to route database alerts to the right team.
Alert Type Reference
The following Mini DBA Azure SQL Database alert detail pages explain why each alert is useful, when to enable it, how to tune thresholds, and what remediation steps to take when the alert is active. Custom Alert is included because each server Alerts page can also hold user-defined query alerts.
| Alert | Category | Detail |
|---|---|---|
| Custom Alert | Custom | Open detail |
| Azure Storage Mb | Open detail | |
| Cpu Per Hour | Open detail | |
| Throttling | Open detail | |
| Wait Ms Per Sec | Open detail | |
| Database Off-line | Availability | Open detail |
| Maximum Connections | Availability | Open detail |
| No Connection | Availability | Open detail |
| Server Latency | Availability | Open detail |
| Cpu % | CPU | Open detail |
| Backup Restore | Disk | Open detail |
| Data File Write Time | Disk | Open detail |
| Data IO % | Disk | Open detail |
| File Size Limit | Disk | Open detail |
| Log Write Time | Disk | Open detail |
| Tran Log % Used | Disk | Open detail |
| Write Log % | Disk | Open detail |
| Buffer Hit Ratio | Memory | Open detail |
| Instance Memory | Memory | Open detail |
| Memory % | Memory | Open detail |
| Page Life Expectancy | Memory | Open detail |
| Plan Hit Ratio | Memory | Open detail |
| Alert Send Error | Monitoring | Open detail |
| Blocked Processes | Query | Open detail |
| Blocking Processes | Query | Open detail |
| Deadlocks | Query | Open detail |
| Long Running Queries | Query | Open detail |
Related Pages
- Alerts
- Copy, Export, And Import Alert Configuration
- Azure SQL logical server alerts
- Alert recipients