The more often you back up your databases and dump your transaction logs, the more data you can recover in case of failure. You must decide how much data you are willing to lose in the event of a disaster and develop a dump schedule to support that decision.
After you schedule your dumps, decide how to incorporate the dbcc commands into that schedule. You do not have to perform dbcc checks before each dump; however, you may lose additional data if a corruption occurs in the dumps.
An ideal time to dump a database is after you run a complete check of that database using dbcc checkstorage and dbcc checkcatalog. If these commands find no errors in the database, you know that your backup contains a clean database. You can correct problems that occur after loading the dump by reindexing. Use dbcc tablealloc or indexalloc on individual tables and indexes to correct allocation errors reported by dbcc checkalloc.
