dcf977e5_ase_Integrity_Checks_Checklist__Item
[#] 5 [Steps] On a good note I have seen a lot of installations where maintenance plans have been setup and integrity checks are being run. The downside is that no one is checking the output and therefore if there are corruption issues no one is aware. So based on this you need to make sure you check the output from the commands to make sure there are not issues. This can be done by piping the output of the commands to a text file, by the built-in reporting option with maintenance plans or by checking your SQL Server error logs. Each time one of these DBCC command is executed an entry is made to the SQL Server error log. After a command is run, you would see something like the following in the SQL Server error log: DBCC CHECKDB (AdventureWorks) executed by Server\DBA found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 31 seconds. [Item] 
Reviewing Output
D e t e r m i n e W h a t i s N e e d e d
U n d e r s t a n d C o m m a n d s
R u n n i n g
S c h e d u l i n g
R e v i e w i n g O u t p u t
H a n d l i n g I s s u e s
SQL Server Database Integrity Checks Checklist
Item