The Azure SQL Database dashboard is the database-level entry point for an individual Azure SQL database. It links to workload, storage, wait, lock, security, and health views for that database.
What To Use It For
- Confirm the database is being monitored.
- Navigate to database summary, activity, queries, waits, locks, and health checks.
- Start database-specific troubleshooting without returning to the logical server page.
How To Use The Azure SQL Database Dashboard
Use the Azure SQL Database dashboard as the starting point when the issue belongs to one database rather than the whole logical server. It brings database-level pages together so you can move from a symptom to the right evidence quickly.
For live slowness, open Azure SQL Activity. For repeated workload cost, use Azure SQL Queries and Azure SQL Query Store. For blocking or concurrency symptoms, open Azure SQL Locks, Azure SQL Waits, or Azure SQL Deadlocks. For capacity and configuration review, start with Azure SQL Database Summary and Azure SQL Health Checks.
The dashboard is also useful after adding a new Azure SQL connection. If the database appears here and the linked pages populate, the connection and permissions are usually working.
Live And Historical Dashboard Data
The Azure SQL Database dashboard includes the Mini DBA Time Range selector. Use Live for current database metrics, or switch to Last Hour, Last 12 Hours, Last Day, Last Week, or Custom to review collected dashboard history. Mini DBA loads and caches the selected historical dataset for the current console session and database context, so chart review stays quick after the range has loaded. Use Back to Live to resume live updates, then select another historical range when you need a different point-in-time view.
Azure SQL Database Dashboard FAQ
Why is the database dashboard separate from the logical server page?
Azure SQL logical servers can host multiple databases. Database-level evidence keeps troubleshooting focused on the affected database.
What if a database is missing?
Check the connection target, database permissions, and collection status. Then review Connect To Azure SQL.
Where should I start during an incident?
Start with Activity for live symptoms, then use Queries, Waits, Locks, or Health Checks based on what you find.