> I noticed this issue across all sql server 2005 servers in our
> environment. When we create maintenance plan (using wizard) for specific
> user database, with database integrity check task included, there is no
> trace of DBCC CHECKDB for that specific database in sql server error
> log. There is only pair of following messages (at the time when
> maintenance plan job is suppose to run):
>
> DBCC CHECKDB (master) WITH no_infomsgs executed by sa found 0 errors and
> repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.
> and
> DBCC CHECKDB (mssqlsystemresource) WITH no_infomsgs executed by sa found 0
> errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 5 seconds.
>
> Again, within CheckDatabaseIntegrity task only specific user database is
> checked. We are NOT specifying master and mssqlsystemresource databases
> when creating maintenance plans!
>
> We use sql server 2005 management studio with service pack 3 installed.
>
> Does anybody have an idea what is going on?

"Erland Sommarskog" wrote:

> Pedja (Pe***@discussions.microsoft.com) writes:
> > I noticed this issue across all sql server 2005 servers in our
> > environment. When we create maintenance plan (using wizard) for specific
> > user database, with database integrity check task included, there is no
> > trace of DBCC CHECKDB for that specific database in sql server error
> > log. There is only pair of following messages (at the time when
> > maintenance plan job is suppose to run):
> >
> > DBCC CHECKDB (master) WITH no_infomsgs executed by sa found 0 errors and
> > repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.
> > and
> > DBCC CHECKDB (mssqlsystemresource) WITH no_infomsgs executed by sa found 0
> > errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 5 seconds.
> >
> > Again, within CheckDatabaseIntegrity task only specific user database is
> > checked. We are NOT specifying master and mssqlsystemresource databases
> > when creating maintenance plans!
> >
> > We use sql server 2005 management studio with service pack 3 installed.
> >
> > Does anybody have an idea what is going on?
> 
> I have an idea, but there is one thing I need to check. Could you post the
> output of SELECT @@version?
>
>
> --
> Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
>
> Links for SQL Server Books Online:
> SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
> SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
> SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>
>

> Pedja (Pe***@discussions.microsoft.com) writes:
>> This si result of select @@version:
>>
>> Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)   Feb  9 2007
>> 22:47:07 
>> Copyright (c) 1988-2005 Microsoft Corporation  Standard Edition on
>> Windows  NT 5.2 (Build 3790: Service Pack 2)
> 
> As I suspected. You confused the issue when you said that you have SP3.
> 3042 is in fact the original version of Service Pack 2, and this
> version had exactly the horrible bug that you have discovered.
>
> As Service Pack 3 recently has been released, I recommend that you download
> and install this version.
>