dcf977e5_ase_Integrity_Checks_Checklist__Item
[#] 1 [Steps] At a high level all databases should be periodically checked for database consistency issues. It is a good practice to run this process during non-peak hours either across the entire database or if you have an extremely large database table by table as time permits. In addition to running this on a set schedule, other times that this would be important to run include a system failure, electrical surge that may have corrupted a write to disk, disk drive failures, the server not being shut down properly or some other hardware failure. For the most part these consistency issues occur when there is some type of hardware failure, so it is a good practice to run these checks as soon as possible if there is a hardware problem or if your database server is not shutdown properly. If your databases are small it is simpler to run the checks across the entire database. With SQL Server 2000 and 2005 maintenance plans the only option is to perform a DBCC CHECKDB so the entire database is checked. Although you do not have the flexibly of using the other options doing something is better then doing nothing. As mentioned above this should be part of your normal database maintenance procedures. If you are not already running integrity checks or if you are not sure, take the time to implement these processes. [Item] 
Determine What is Needed
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