Forgot something that I do on 2005. I have all my 2005 instances set to use checksums for torn page detection, so I run the following code in addition to my DBCC step:

select * from msdb..suspect_pages

go

The output goes into a text file, suspectpagesresult.txt. If I get any rows in my result, I know I have a problem (haven't gotten any yet).

I also filter my DBCC runs

d:

cd\dbccs

type dbccresult.txt | find "errors" >server1_dbcc.txt

type suspectpagesresult.txt >>server1_dbcc.txt

So my result file looks someting like this:

....

DBCC Results:

CHECKDB found 0 allocation errors and 0 consistency errors in database

CHECKDB found 0 allocation errors and 0 consistency errors in database

CHECKDB found 0 allocation errors and 0 consistency errors in database

CHECKDB found 0 allocation errors and 0 consistency errors in database

CHECKDB found 0 allocation errors and 0 consistency errors in database

CHECKDB found 0 allocation errors and 0 consistency errors in database

CHECKDB found 0 allocation errors and 0 consistency errors in database

CHECKDB found 0 allocation errors and 0 consistency errors in database

CHECKDB found 0 allocation errors and 0 consistency errors in database

CHECKDB found 0 allocation errors and 0 consistency errors in database

1> 2> 1> 2> 3> database_id file_id page_id event_type error_count

last_update_date

----------- ----------- -------------------- ----------- -----------

-----------------------

(0 rows affected)

1>

Makes things a lot easier to see if there are problems rather than sifting through pages of DBCC results. If I see a non-zero result, I know there is a problem and I have the full log on my server to investigate further.