Post reply

95 GB Transaction Log but Log Backups are much smaller

  • April 9, 2014 at 10:39 am

    #1704606

    No, don't. It's not necessarily the blocking session which is causing the large log. It's an active transaction. It may be the same session, it may not.

    What does DBCC OPENTRAN return?

    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

  • April 9, 2014 at 10:50 am

    #1704611

    Hi Gail,

    Thanks for the suggestion. Here you go:

    Oldest active transaction:

    SPID (server process ID): 507

    UID (user ID) : -1

    Name : user_transaction

    LSN : (86450:32972:1)

    Start time : Apr 5 2014 10:10:32:687PM

    SID : 0x175cce5b0a5e7e478614a5b3d139fac8

    --Karen

  • April 9, 2014 at 11:00 am

    #1704618

    Ok, so it is session 507 which has had an active transaction since the 5th of April (last week friday)

    You may want to do some investigation as to how and why the session has an open transaction that long, so that you can ensure it doesn't happen again, then kill 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

  • April 9, 2014 at 1:09 pm

    #1704665

    Thanks Gail, will do.

Viewing 4 posts - 16 through 18 (of 18 total)

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