What are the challenges you face when working across database platforms? Take the survey

Transaction Log not truncating?

sunbakedsunbaked Posts: 12
edited September 28, 2009 1:13AM in SQL Backup Previous Versions

I must be doing something wrong but doing a Transaction Log backup with "Remove inactive entries from transaction log" checked does not truncate my log file. With v5 we had been doing the log backups using SQL itself because of this but after upgrading to v6 i was hoping to get away from this. Can you please advise and let me know what to try. Thanks.



  • Options
    peteypetey Posts: 2,358 New member
    Truncating the transaction log is a logical operation, and will not affect the physical transaction log file size, unless the database has the autoshrink property set.

    Shrinking the transaction log is a physical operation, and will reduce th size of the transaction log file where it's possible to do so. See here for details.

    Setting the 'Remove inactive entries from transaction log' option causes SQL Server to truncate the transaction log after the backup, which is the 'normal' process for a transaction log backup.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
Sign In or Register to comment.