Azure SQL Files shows database file information for an Azure SQL database, including file name, type, size, and physical name where available.
Use This Page To
- Review data and log file size.
- Understand storage use.
- Compare file data with summary storage.
- Investigate storage-related alerts.
Workflow
- Open the Azure SQL database.
- Select Files.
- Review file size and type.
- Compare with Database Summary storage values.
- Check Elastic Pools for pool-level storage pressure.
How To Use Azure SQL File Information
Azure SQL Files provides storage context for a database. Use it when storage alerts fire, when a database is approaching capacity, or when you need to explain data and log growth during a performance incident. The page helps connect database-level storage to the summary and alert pages.
Review data and log size separately. Data growth may be normal business growth, an unexpected import, a retention issue, or a schema change. Log growth may relate to transaction volume, long-running transactions, index maintenance, or bulk changes. Compare file evidence with Azure SQL Database Summary, Azure SQL Activity, and Azure SQL Alerts.
For databases in elastic pools, storage and resource pressure may need to be reviewed at pool level as well as database level. Open Azure SQL Elastic Pools when several databases share the same pool.
Azure SQL Files FAQ
Why does file size matter in Azure SQL?
File size helps explain capacity alerts, growth patterns, and whether a database is approaching limits for its configured tier or pool.
Should I shrink files after growth?
Not automatically. Shrinking can cause fragmentation and may not solve the reason the database grew.
Where should I investigate sudden growth?
Check Activity, Queries, alerts, recent deployments, imports, retention jobs, and index maintenance.