Azure SQL Logical Server Alerts show alert records associated with a monitored Azure SQL logical server. Use this page to focus on server-level Azure SQL conditions before drilling into a database.
Workflow
- Open the Azure SQL logical server.
- Select Alerts.
- Review alert severity, message, and time.
- Open Databases or Elastic Pools for supporting data.
- Configure or copy alert policy from the child database or elastic pool alert page.
- Use global Alerts for cross-engine alert triage.
How To Use Logical Server Alerts
Logical server alerts help you review Azure SQL conditions that may affect more than one database or elastic pool. Use this page when the issue appears to be related to the Azure SQL logical server, shared configuration, or a group of databases rather than one database only.
Start with high-severity and recurring alerts. Then decide whether the alert should be investigated at the logical server level, database level, or elastic pool level. Database-specific alerts are usually easier to investigate from Azure SQL Database Alerts, while pool pressure belongs with Azure SQL Elastic Pools.
Logical server alerts are also useful for managed service review because they show a concise server-level history. Capture the alert time, affected databases or pools, owner, and resolution so repeated patterns can be reduced.
This page is a roll-up view. To copy, export, or import alert configuration, open the individual Azure SQL database or elastic pool Alerts page and use Configure and Copy Config. See Copy, Export, And Import Alert Configuration.
Logical Server Alert FAQ
When should I use this page instead of database alerts?
Use it when the condition affects the logical server, several databases, or an elastic pool. Use database alerts for one affected database.
Can Azure SQL alerts show root cause?
Alerts point to a condition. Use database, pool, query, wait, and health pages to confirm the cause.
How should alerts be routed?
Use Alert recipients and recipient groups so Azure SQL alerts reach the right application or DBA team.
Azure SQL Alert Type Reference
Azure SQL logical server alert management uses the Azure SQL Database alert definitions because Mini DBA evaluates alert conditions against monitored Azure SQL database resources. Use the detail pages below when deciding which alerts to enable across all databases hosted on the selected logical server. Custom Alert is included because Azure SQL alert lists 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 |