SQL Scripts: How To Find Data And Log File Information

As a DBA, one of the things I routinely need to check is how much space is available in my database data and log files.  In this post of my ongoing SQL Scripts series, we will take a look at a script that gives us some insight into these files in our database.

Why Should I Check The Size Of My Database Files?

The size of your database’s data and log files may not be an accurate representation of the actual size of your data.  For example, a log file may grow, and then get truncated, but the size of the log doesn’t shrink. There can be a big difference between the space the files physically consume on disk, and the amount of data actually in those files. Many DBAs like to initially create their data/log files large with a lot of free space and allow them to fill up over time as the data grows.

You also want to see if your database files are getting close to full, and try to head off any auto-growth events by manually increasing the size of your files before SQL Server is forced to do it on its own.  I always try to keep an eye on this, so I can manually grow my files during a maintenance window instead of letting SQL Server do it during normal operating hours.

How Do I Find My Data And Log File Information?

The query below will check the built in sys.database_files DMV to return information about the data and log files associated with a given database.  The DMV actually returns the size of the file in 8-KB pages, so my query does the calculations to convert that to megabytes and percentages, as well as also providing the current auto-growth settings for each file.


This post is part of an ongoing SQL Scripts series, in which I list useful queries that I use in my day to day database administration.


(Visited 1,952 times, 1 visits today)

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.