Post reply

Full Transaction Log, Database in Simple Mode

  • July 27, 2012 at 3:13 am

    #392844

    Hi All

    Looking for some guidance on how to determine the source that is causing the transaction log to fill up.

    I have a database called productupdates and the mdf is 16GB in size, It is set to simple recovery mode.

    If transaction log is set to unrestricted growth, it grows to over 11GB if left within a day or so.

    If we limit the transaction log the backup fails stating that the log is full.

    Any help would be much appreciated.

    Thanks

    Steve

  • July 27, 2012 at 3:47 am

    #1518372

    There could be many cuases for this. There really isn't enough information here to narrow it down. It could be due to the size of the inserts/updates to table(s) in the database, or maintenance processes such as index rebuilds.

    Does the database participate in replication in any way? That could cause it as well.

  • July 27, 2012 at 4:02 am

    #1518377

    Hi

    There is no replication.

    Is there a sql script that I could run to show me what is filling the log up or what job/sproc is causing it to fill up?

    What info do you need to help identify the issue?

    Thanks

    Steve

  • July 27, 2012 at 5:08 am

    #1518408

    Please read through this: http://www.sqlservercentral.com/articles/Transaction+Log/72488/

    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 4 (of 4 total)

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