Post reply

Truncate log question

  • March 1, 2012 at 6:32 am

    #269329

    Hi all

    We have restored a large DB into a DEV environment and changed the recovery model to simple. We then wanted to shrink the log however it is not letting me do this and using DBCC LOGINFO I can see nearly all the log has a status of 2 which means it is active.

    I had though that changing the DB to simple would mark this an inactive and allow me to shrink the log, but that doesn't seem to be the case. I have also run DBCC OPENTRAN and get the following:

    Transaction information for database 'xxx'.

    Replicated Transaction Information:

    Oldest distributed LSN : (196903:14468:10)

    Oldest non-distributed LSN : (196903:16446:3)

    DBCC execution completed. If DBCC printed error messages, contact your system administrator.

    How can I mark the log as in active. I am trying to avoid a full back due to the size of it, also I didn't think I would have to do that anyway.

    Further to this, the DB in question is being used as a publisher in replication, what impact does this have on the DB when in simple recovery.

    Thanks

  • March 1, 2012 at 7:29 am

    #1453614

    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

  • March 1, 2012 at 8:27 am

    #1453671

    Hi - Seems the log reader agent had been stopped, I did a re-initialise and was then able to shrink the log.

    Thanks

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

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