If you run DBCC CHECKDB and it finds corruption in the database the last line of output will state something like "CHECKDB found x allocation errors and x consistency errors in database."
My question is, when this happens in a SQL maintenance plan or SQL Agent job will it be handled as a failure similar to if the DBCC actually fails (ex. lost connectivity)?
I'm presumming it wouldn't since the DBCC is just returning information...it doesn't care if the information is good or bad news right? If my presumption is correct then that really bites since the operator still has to scan the entire result message proactively to confirm whther or not the db has any corruption problems.