Article ID: 873235 - View products that this article applies to.
Full transaction logs can make your Microsoft SQL Server database unusable. This article describes how to truncate and shrink the transaction logs when they grow too large. This article also describes how to prevent the transaction logs from growing unexpectedly.
Step one: Reduce the transaction log size
Step two: Truncate the inactive transactions in your transaction log
Step three: Shrink the transaction log file
Step four: Prevent the transaction log files from growing unexpectedly
More information about transaction log files
For more information about how to reduce the transaction log size, visit the following Microsoft websites:
For more information about troubleshooting the additional disk space requirement during the recovery process, see the "Insufficient disk space" topic in SQL Server Books Online. For more information about the transaction log architecture, see the following topics in SQL Server Books Online:
Article ID: 873235 - Last Review: July 12, 2013 - Revision: 9.2
Contact us for more help