Post reply

DBCC CHECKDB

  • July 9, 2005 at 1:57 am

    #363107

    Hi,

    Last time when i ran DBCC CHECKDB <database name>, it took 2 hrs to complete and didnt report any errors.

    Today i'm running checkdb on the same database but i have added one more option i.e. i'm executing DBCC CHECKDB (database name,repair_fast).

    Now this is running for past more than 2.5 hrs now . Is it expected to take more time provided database has NO ERRORS?

    Also, can we cancel the execution in the middle? What consequences this may have on the database?

    Thanks in advance.

     

  • July 12, 2005 at 8:00 am

    This was removed by the editor as SPAM

  • July 12, 2005 at 10:53 am

    #573559

    How big is the particular DB, and what procs are running against it when your CHECKDB is invoked?  What's curious is the 2.5hrs for the repair_fast, which requires the DB be in single user mode.

    I run the same DBCC one/wk, and even on the biggest of mine (4GB), it finishes in a coupla minutes.

  • July 12, 2005 at 12:50 pm

    #573633

    Just my 2 cents, but I'd be very reluctant to cancel the process with any of the repair options turned on.  The result may leave the database in an inconsistent state and require a recovery from backup.

    That said, 2.5 hours is a long time.  How large is the DB?  And just curious, but if the dbcc's reported no errors, why did you select to run it with the repair option?  Is there some other behavior that makes you think there's something wrong with the database? 

    My hovercraft is full of eels.

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

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