We have a corrupt database and are trying to repair it. I execute the following command in Query Analyzer: "DBCC CHECKDB ('CriticalDB', REPAIR_FAST) WITH ALL_ERRORMSGS ". It has been running for 45 minutes with no visible sign of progress. We had no idea it would take so long and are sorry we tried this. We would rather rebuild manually the suspect tables or indexes at this point, but we are afraid to stop the query for fear of causing more damage to the database. Is it safe to stop execution of this query? Thanks!
2007-02-01 06:57:23 · 2 answers · asked by sideshot72 3 in Computers & Internet ➔ Programming & Design
According to MSDN, the REPAIR_FAST directive does not perform any repair actions. I'm not exactly sure why they called it that if it doesn't repair, but that's what it says. So, you should be able to terminate the process... it is only analyzing your database, not making changes.
If your database is especially large or complex, it can take a very long time to run those processes, though.
2007-02-01 08:02:40 · answer #1 · answered by Rex M 6 · 0⤊ 0⤋
I suppose that it is safe to stop execution of this query.
2007-02-02 23:18:57 · answer #2 · answered by Serge M 6 · 0⤊ 1⤋