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.
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.
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.