Conditions for backing up the transaction log

  • Hi,

    I would appreciate if somebody shed light on the following.

    BOL states:

    "Do not back up the transaction log if the transaction log has been explicitly truncated, unless a database or differential database backup is created after the transaction log truncation occurs."

    Is BOL stopping you from backing up the transaction log if it has been manually truncated because such a transaction log would be of little use or is there some other reason for it?

    Please clarify.

    Karim

  • I think you've hit the nail on the head.  There would be missing transactions in the middle (those that were truncated) that were never backed up into a log.  Thus the chain of incremental logs is broken...  Taking a full or differential backup would act as a new anchor for new transaction log backups - as the given advice from BOL says...

    MS probably could've spelt it out better       But then we wouldn't have so many of these wonderful forums!

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply