dcf977e5_ase_Integrity_Checks_Checklist__Item
[#] 4 [Steps] The best time to run these commands for normal periodic checking is during low usage times. Using SQL Server Agent is the best approach so you can schedule the jobs to run at any time. If your hardware is pretty stable and you have not had any issues you could probably run these checks either weekly or monthly. Hardware has come along way and it is much less likely to have issues like in the past. Even so, it is still a good idea to make this a part of your regular DBA procedures. If you have ongoing hardware problems or your systems not very stable it is a good idea to run these checks more frequently. If you do encounter any problems you want to catch them as soon as possible before the corruption spreads throughout the entire database. [Item] 
Scheduling
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