May 9, 2007 at 11:30 am
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
May 11, 2007 at 8:40 am
A little more info. I have narrowed down the issue to one table. That table has a clustering index, and 3 non-clustered indexes. It has 43,000,000 rows. I ran DBCC CHECKTABLE PHYSICAL_ONLY and it runs OK. I ran DBCC CHECKTABLE NOINDEX and it runs OK. Full DBCC CHECKTABLE never finishes, I killed it after 6 hours. I was able to drop the 3 non-clustered indexes, but I tried to drop the clustered index and it also ran for over an hour before I killed it. I will try again over the weekend when I have more time.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply