To check for corruption on a very large production database I created a database-snapshot to run CHECKDB against.
This found a corrupt-table (“CHECKDB found 0 allocation errors and 4191 consistance errors in table … repair_allow_data_loss is the minimum repair level for the erors found…”).
I tried running CHECKTABLE against the suspect table within the live database, but couldn’t due to lack of space.
Finally I used DBCC CHECKTABLE(sometablename) WITH TABLOCK so dbcc wouldn’t create a background copy on the database to check – and run out of space!
This confirmed the live table was fine (yay! ooo cake).