I have a very large database (233GB), and running DBCC CHECKDB with REPAIR_ALLOW_DATA_LOSS is taking WAY too long (over 15 hours). There are a lot of indexes on a table that I would rather have removed, but cannot remove the table until the database is back up and running. Each index is taking AT LEAST 2 hours to check. Is there a way to run CHECKDB with both REPAIR_ALLOW_DATA_LOSS AND NOINDEX?
Asked
Active
Viewed 284 times
0
-
What database are you using? – kasperd Dec 27 '14 at 18:15
-
I am using MSSQL 10 – Walter Zydhek Dec 27 '14 at 18:55
-
1You should add that information to the question and apply some relevant tags. – kasperd Dec 27 '14 at 19:02
1 Answers
0
When you run DBCC CHEKDB with NOINDEX then, it skips indexes completely. NOINDEX does not affect system tables because integrity checks are always performed on system table indexes.
Check this reference.
Glorfindel
- 1,213
- 4
- 15
- 22
Priyanka
- 1
- 1