Azure SQL Tables shows table information for a selected Azure SQL database. Use it during database review, query investigation, and schema-oriented troubleshooting.
Use This Page To
- Review table names and metadata.
- Support query and index investigations.
- Find objects involved in locks, deadlocks, or expensive statements.
- Navigate from workload symptoms to schema context.
How To Use Azure SQL Table Context
The Tables page is most useful when performance evidence points to a specific object. After identifying a high-impact statement in Azure SQL Queries, use this page to confirm the table name and move into supporting schema checks. When lock or deadlock evidence names an object, the Tables page helps connect that symptom to the database structure the application is using.
Table inventory also helps during capacity and migration reviews. Large or heavily used tables may deserve closer inspection in Azure SQL Indexes, Azure SQL Query Store, and Azure SQL Database Summary. If a table is unexpectedly missing, verify you are viewing the correct Azure SQL database, not just the correct logical server.
Use table information as context rather than a tuning recommendation by itself. The right action depends on workload, indexes, query plans, data volume, and business use.
Azure SQL Tables FAQ
Is the Tables page a schema design tool?
No. It provides monitoring and inventory context. Apply schema changes through your normal database change process.
Why does table visibility differ between databases?
Permissions, database selection, and Azure SQL metadata visibility can affect what the monitoring login can see.
Where should I go after finding a relevant table?
Open Azure SQL Indexes, Azure SQL Queries, or Azure SQL Locks, depending on the symptom.