The SQL Server Files page shows database file information for the monitored instance. Use it to review file sizes, growth, placement, and capacity risk.
What You Can Review
- Database data files.
- Database log files.
- File size and growth information.
- File placement by drive.
- Capacity trends and possible storage risks.
Workflow
- Open Files for the SQL Server.
- Sort by database, file size, drive, or growth.
- Compare file placement with Drives.
- Check Waits for I/O pressure.
- Use Database detail for database-specific file context.
How To Review SQL Server Files
SQL Server file information helps explain storage capacity, growth, and placement risks. Use this page when a drive alert fires, a database grows unexpectedly, log reuse is blocked, or I/O waits suggest storage pressure. Reviewing files across the instance helps you see which databases are using each drive.
Separate data-file growth from log-file growth. Data growth can come from normal business activity, imports, retention issues, or new tables. Log growth can come from long transactions, recovery model behavior, backups, index maintenance, or bulk changes. Compare file data with SQL Server Drives, SQL Server Waits, and SQL Server Database Detail.
Avoid shrinking files as a reflex. Shrinking can create fragmentation and may not fix the cause of growth. Investigate the workload and retention pattern first.
SQL Server Files FAQ
Why review file placement?
File placement helps identify whether data, log, tempdb, backup, or system files share constrained storage.
Does a large log file always mean a problem?
No. Size must be interpreted with recovery model, backup frequency, transaction behavior, and expected workload.
What should I check during sudden file growth?
Review active sessions, recent jobs, imports, index maintenance, backups, and application deployments.