Maint Plan via wizard, doesnt show bad db when it actually is..

Win2003Stdx64sp2,sql2005x64sp2

I setup maintenance job to do database checks via the wizard to do all user db's (and tired specific too). I downloaded a corrupt database (Broke) from msdn blog area. Ran the job, but it did not find the error as I would have hoped. Ran check in QA and got the error as expected…Am I missing something? I was hoping it would be similar to 2000 and state a failure if there was and error found.

Job report:

NEW COMPONENT OUTPUT
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.3042 Report was generated on " XXXXXXXX ".
Maintenance Plan: User_MaintPlan_CheckDB
Duration: 00:00:12
Status: Succeeded.
Details:
Check Database Integrity (XXXXXXXX)
Check Database integrity on Target server connection Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Include indexes
Task start: 2007-05-08T11:14:53.
Task end: 2007-05-08T11:15:03.
Success
Command:USE [ReportServer]
GO
DBCC CHECKDB WITH NO_INFOMSGS
GO
USE [ReportServerTempDB]
GO
DBCC CHECKDB WITH NO_INFOMSGS
GO
USE [AdventureWorksDW]
GO
USE [Broke]
GO
DBCC CHECKDB WITH NO_INFOMSGS
======================================

Then I ran this in QA:

USE [Broke]
GO
DBCC CHECKDB WITH NO_INFOMSGS

QA Results:

Msg 8928, Level 16, State 1, Line 1
Object ID 2073058421, index ID 0, partition ID 72057594038321152, alloc unit ID 72057594042318848 (type In-row data): Page (1:143) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 2073058421, index ID 0, partition ID 72057594038321152, alloc unit ID 72057594042318848 (type In-row data), page (1:143). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.
CHECKDB found 0 allocation errors and 2 consistency errors in table 'brokentable' (object ID 2073058421).
CHECKDB found 0 allocation errors and 2 consistency errors in database 'Broke'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Broke).

Itappears to be an issue with sp2 and doing muplitle db. I was at sp2 (3042) I applied GDR2 now at 3054. It is now showing the error in the maint job but it appears to be stopping after it finds the error and not finishing.

NEW COMPONENT OUTPUT

Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.3054 Report was generated on "XXXXXXXXXXXXX".

Maintenance Plan: User_MaintPlan_CheckDB

Duration: 00:01:08

Status: Warning: One or more tasks failed..

Details:

Check Database Integrity (XXXXXXXXXXX)

Check Database integrity on Target server connection Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.

Databases: All user databases

Include indexes

Task start: 2007-05-08T18:20:05.

Task end: 2007-05-08T18:21:11.

Failed-1073548784) Executing the query "DBCC CHECKDB WITH NO_INFOMSGS " failed with the following error: "Object ID 2073058421, index ID 0, partition ID 72057594038321152, alloc unit ID 72057594042318848 (type In-row data): Page (1:143) could not be processed. See other errors for details.

Table error: Object ID 2073058421, index ID 0, partition ID 72057594038321152, alloc unit ID 72057594042318848 (type In-row data), page (1:143). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.

CHECKDB found 0 allocation errors and 2 consistency errors in table 'brokentable' (object ID 2073058421).

CHECKDB found 0 allocation errors and 2 consistency errors in database 'Broke'.

repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Broke).". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

|||I doubt due to the backward compatibility issues running it from sql 2005 towards sql 70, you might need to depend upon SQL Enterprise manager to tackle such maintenance plans on ver.70 databases.