• You guys are concentrating on the wrong thing here. it is not running DBCC consistency checks regularly on your database that is the real issue of importancy here. Most competent and veteran DBA's are doing this anyway. It is the rash and foolish actions that many take after they see the results of running DBCC checks that make things much much worse. First thing. don't panic and do something stupid after looking at the results of a DBCC command!!! Paul Randal talks about this constsntly ad nauseum in his seminars and on his blogs. He wrote DBCC CHECKDB so believe me he would know. DBCC CHECKDB is a powerful tool, but it is also very dangerous in the wrong hands. There is a great article below on the use and abuse of DBCC. Also, to the VLDB issue, you can run DBCC CHECKFILEGROUP on the INDIVIDUAL filegroups (which you should be using on a VLDB anyway) which cuts that VLDB up into smaller more manageable chunks..Justifying not performing a DBCC check because the database is just too big and takes too long is foolish and lazy IMHO. HTH. 😀

    http://www.sql-server-pro.com/dbcc-checkdb.html

    "Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ...:-D"