Post reply

The transaction log for database is full

  • July 22, 2012 at 8:33 pm

    #1516051

    Application was issuing a DELETE on 4 mil rows on a table that caused the log to full....Easy solution was just to truncate those records so when the application start next time, didn't have anything to delete and it worked like a charm....Thanks to Gail for pointing to the right direction.

  • July 23, 2012 at 3:36 pm

    #1516495

    Gail, one thing though could I have used profiler instead of DMv to troubleshoot this? Which template would be best to troubleshoot this?

  • July 23, 2012 at 3:39 pm

    #1516497

    Possibly, but it would have been a lot harder. Profiler doesn't ahve anything that tells you how much log space is/was used by a session. That's the benefit of the DMVs, you could have just put a polling process in place to log to a table any queries using more than x kb of log space if you'd needed to monitor for a while.

    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

  • July 23, 2012 at 3:42 pm

    #1516498

    I see. Thanks for your response again.

Viewing 4 posts - 46 through 48 (of 48 total)

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