Azure SQL Database Summary shows service, storage, configuration, and access information for one Azure SQL database.
What You Can Review
- Service tier, service objective, compute tier, DTU limit, cores, and elastic pool.
- Allocated storage, used storage, log usage, and state.
- Compatibility level, collation, statistics settings, broker state, read-only state, and log reuse wait.
- Access level and key monitoring permissions.
Workflow
- Open the Azure SQL database.
- Select Database Summary.
- Confirm service and storage values match expectations.
- Review access indicators if other pages show missing data.
- Continue to Activity, Queries, or Health Checks.
How To Use Azure SQL Database Summary
Database Summary is the best first page for understanding the configuration and capacity of one Azure SQL database. Use it before deeper troubleshooting so you know the service tier, compute model, storage limits, compatibility level, and permission indicators for the database you are reviewing.
For performance issues, service objective and elastic pool membership matter. A database can look slow because it is underprovisioned, because it shares a busy pool, or because a query plan changed. Use Summary to confirm the environment, then move to Azure SQL Activity, Azure SQL Queries, Azure SQL Query Store, and Azure SQL Waits.
For permission issues, access indicators can explain why related pages are incomplete. If data is missing, compare this page with Azure SQL Permissions and Connect To Azure SQL.
Azure SQL Database Summary FAQ
Why does service tier matter for troubleshooting?
Service tier controls available resources and limits. Performance evidence should be interpreted against the configured tier or pool.
What if storage values look wrong?
Compare Summary with Azure SQL Files, alerts, and recent data growth or maintenance activity.
Why review permissions here?
Permission indicators help explain whether missing monitoring data is caused by access rather than workload.