We are using DBCC CHECKDB on a VLDB 1TB in size. Previously when on our 2008 platform the check ran successfully on a drive that was 150GB in size for TempDB, but since moving to SQL 2012 and AlwaysOn the check is now running out of space on a 200GB drive.

The DBCC CHECKDB with ESTIMATEONLY is returning a value of 1, so I think we are suffering from what some have said is a bug in that command.

Does CHECKDB work differently between SQL versions?

P.S. I know a work around is to break up the check into batches but we are wanting to know why this has become an issue now.

  • As far as I know, ESTIMATEONLY is bugged. Some says it was fixed in 2012 version with sp2, some say no. Was 2008 version r2? Has database in SQL 2012 heavy activity? – user_0 Aug 10 '15 at 12:28
  • At the time the DBCC runs theres not a lot else going on no. – Tom Aug 10 '15 at 13:02
  • 1
    What is the waittype when you are running CHECKDB ? Are you having any blobs or non-clustered indexes on computed columns or sparse columns in your database ? – Kin Shah Aug 10 '15 at 13:25
  • Sorry for the slow response, I will check out what columns there are in our largest table. – Tom Aug 13 '15 at 8:31

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.