Post reply

Transaction log backup problem

  • October 30, 2012 at 8:05 am

    #283840

    I'm feeling rather slow this morning that I can't figure this out without help but here goes.

    I have a database where the log is full. The log_reuse_wait_desc is showing LOG_BACKUP. However I just finished running a log backup. Can anyone tell me why this would still be here? And what I can do to clean up the log at this point?

    Thanks

    Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]

  • October 30, 2012 at 10:36 am

    #1554264

    Log_reuse doesn't change instantly. Wait a bit, run a checkpoint if you want to hurry things along, then check what it says after that. Also check to make sure that log backup you just run didn't have either COPY_ONLY or NO_TRUNCATE in it.

    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

  • October 30, 2012 at 12:07 pm

    #1554308

    You were right. I checked again and everything was fine. I'll remember the checkpoint for next time though.

    Thanks!

    Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]

  • October 30, 2012 at 12:10 pm

    #1554310

    You don't need to run a checkpoint. All you need to do is wait a bit. Forcing a checkpoint just makes SQL re-check and update the DMV (well, simplifed)

    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

Viewing 4 posts - 1 through 3 (of 3 total)

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