How often should I perform dbcc?
How often depends on how much data you are willing to lose in a worst-case scenario. In general, the more important your data, the more often you should run dbccs. If yours is not a 24-hour organization, and dbccs will complete during your down-time, perform them nightly with the output redirected to a file. Perform a grep on the file for the keywords “Err,” “err,” and “Msg” to catch most errors that dbcc would report. Scan the output occasionally to catch anything else that might be reported. Mission-critical enterprises often use a second server as a “warm backup.” Instead of running dbcc commands on the production server, dumps are taken, loaded on the warm backup, and dbccs are run there. If errors are discovered, attempts are made to correct it on production server. Sites with very large databases sometimes use a rotating schedule of dbcc tablealloc and dbcc checktables, rather than the all-at-once dbcc checkalloc and dbcc checkdbs. Additionally, a new command, dbcc checkstorage,
