Skip to content

SQL Server Transaction Log File (LDF) Misconception

Sponsor: Do you build complex software systems? See how NServiceBus makes it easier to design, build, and manage software systems that use message queues to achieve loose coupling. Get started for free.

Learn more about Software Architecture & Design.
Join thousands of developers getting weekly updates to increase your understanding of software architecture and design concepts.


A common misconception is that setting the recovery model to simple will cause SQL Server not to use the transaction log file (LDF), preventing it from growing to an abnormal size. In fact, the simple recovery model will still use the transaction log when performing transactions, however it will reclaims log space to keep space requirements small. The actual file size will not be reduced by reclaiming space.  Same as performing a transactional backup will not reduce the actual file size. This is important becase if you have a long running transaction that is performing many insert/update/delete statements, the transaction log file could grow (depending on settings) to a very large size.  Once it has grown, it will stay that size until you shrink the log file.

Leave a Reply

Your email address will not be published. Required fields are marked *