Post reply

Why is my transaction log full?

  • November 22, 2012 at 11:23 am

    #1561687

    Has the DB just been switched from full or bulk-logged recovery? If so, run a checkpoint, sys.databases is not updated immediately, hence you can get 'log backup' occurring for a very short period after the DB has been switched to simple recovery model.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • November 22, 2012 at 1:07 pm

    #1561706

    Artoo22 (11/22/2012)

    Log backup

    The log backup wait reason will never appear in Simple Recovery.

    Now I do agree this is a valid statement, however:

    Actually, that's not an accurate statement. This column records the reason the log file could not be truncated the last time it tried to do so. In simple recovery model, this means that it gets updated, if there is a reason, when a checkpoint occurs.

    For example:

    My blog: SQL Soldier[/url]
    SQL Server Best Practices:     SQL Server Best Practices
    Twitter: @SQLSoldier
    My book: Pro SQL Server 2008 Mirroring[/url]
    Microsoft Certified Master: SQL Server, Data Platform MVP
    Database Engineer at BlueMountain Capital Management[/url]

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

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