Microsoft KB Archive/272318

= INF: Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE =

Article ID: 272318

Article Last Modified on 11/6/2003

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition

-



This article was previously published under Q272318



SUMMARY
Shrinking the log in SQL Server 2000 is no longer a deferred operation. A shrink operation attempts to shrink the file immediately. However, in some circumstances it may be necessary to perform additional actions before the log file is shrunk to the desired size.



MORE INFORMATION
When DBCC SHRINKFILE is run, SQL Server 2000 shrinks the log file by removing as many virtual log files as it can to attempt to reach the target size. If the target file size is not reached, SQL Server places dummy log entries in the last virtual log file until the virtual log is filled and moves the head of the log to the beginning of the file. The following actions are then required to complete the shrinking of the transaction log:
 * 1) You must run a BACKUP LOG statement to free up space by removing the inactive portion of the log.
 * 2) You must run DBCC SHRINKFILE again with the desired target size until the log file shrinks to the target size.

The following example demonstrates this with the pubs database and attempts to shrink the pubs_log file to 2 MB:   Run this code:

DBCC SHRINKFILE(pubs_log, 2) NOTE: If the target size is not reached, proceed to the next step.   Run this code if you want to truncate the transaction log and not keep a backup of the transaction log. Truncate_only invalidates your transaction log backup sequence. Take a full backup of your database after you perform backup log with truncate_only:

BACKUP LOG pubs WITH TRUNCATE_ONLY

-or-

Run this code if you want to keep a backup of your transaction log and keep your transaction log backup sequence intact. See SQL Server Books Online topic &quot;BACKUP&quot; for more information: BACKUP LOG pubs TO pubslogbackup   Run this code: DBCC SHRINKFILE(pubs_log,2) The transaction log has now been shrunk to the target size. 