Has anyone ever had a DBCC CHECKDB run time increase excessively? My CHECKDB, which runs once a week, was running in about 3 hours on a 180Gb database. Last weekend it ran for 33 hours, and spat out some consistency errors on one table. I tried running CHECKTABLE on that one table and it ran for 6 hours, on a 58Gb table before I gave up. I ran with PHYSICAL_ONLY and it ran OK. I was able to rebuild all the indices on the table with no issue.
I suspect I have some corruption but I'm not sure...
SQL 2000 SP4