SQL 2005: Truncating Log Files and Recovering Space
April 4, 2008 · Print This Article
A common issue for users of SQL Server databases is disk space and the size of the physical log file and database. While we’re not going to attempt to make “one size fits all” statement on database maintenance plans, we though it would be helpful to provide a few suggestions that will help you trim the size of your files when you are in a pinch.
Steps to truncating log files and shrinking your database:
1. Get the physical names of your database file (MDF) and log file (LDF):
Run the following system stored procedure:
This command will return a variety of information, including the physical size (the “size” column) and the path and name of your database and log files (in the “filename” column).
Record the name of the file from the “filename” colunm, excluding the path and file extension (e.g. if filename contains “C:\sqldatabases\yourdatabase_data.mdf” you want to save the string “yourdatabase_data”)
2. Truncate the database and shrink the database
The following set of SQL will shrink your database and “truncate” the log file. File in the parmaters surrounded by <…>. Note that you’ll need the two filename values from step 1.
BACKUP LOG <yourdatabasename> WITH TRUNCATE_ONLY
DBCC SHRINKFILE (<yourdatabaselogfilename>, 1)
DBCC SHRINKFILE (<yourdatabasedatafilename>, 1)
When complete, this script will output the same information as in step 1. Compare the new size with the old.