There are many times that CheckDB ends up being extremely slow, sometimes taking more than a day to run. This can make life difficult if you are trying to find out what is corrupt.
DBCC CheckDB(MyBigDatabase) WITH NO_INFOMSGS;
There are several of the tricks that I use to speed up DBCC CheckDB, depending on the specific environment. What I am looking for is what others do when they need to run DBCC CheckDB on a big database that appears to take forever to complete?
All answers posted by the end of Database Corruption Challenge 6 will earn an extra point in the Database Corruption Challenge. As part of the Database Corruption Challenge it is not feasible for me to create a 3TB database file and expect anyone to want to download it for the challenge. I would love to do that, however I don’t think anyone would participate in the Corruption Challenge if you had to download a 3TB file.
If you need details on finding out what table CheckDB is stuck on (or currently processing) you can take a look at my Status of DBCC Check DB blog post. Included in the post are queries to find the table currently being checked by DBCC CheckDB, which is particularly useful when you have a slow CheckDB process running.
So, what have you done speed up DBCC CheckDB, and why?