Post reply

DBCC CHECKDB and Transactions Rolled Forward/Back

  • December 10, 2008 at 9:45 am

    #198824

    Can anyone tell me if the DBCC CHECKDB command would cause entries in the Event Log stating transactions were rolled forward and back?

    I have a backup job that checks database integrity beforehand and I see in the Event log at that time an entry for the DBCC CHECKDB command and immediately after an entry for # of trans rolled forward and an entry for, usually 0, trans rolled back.

    Just making sure that the dbcc command is causing these messages and it's normal to see them.

    Thanks!

  • December 10, 2008 at 12:22 pm

    #910602

    Normal. The DBCC command is causing the rollback/forward messages.

  • December 10, 2008 at 12:30 pm

    #910609

    Thank you!

  • December 10, 2008 at 12:37 pm

    #910614

    One thing to note is that no transactions are actually rolled back. What checkDB is doing is creating a hidden database snapshot to do the check on and the transactions are rolled back only in the context of that snapshot, not in the real DB.

    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