dbTalk Databases Forums  

No trace of maintenance plan checkdb in sql server error log?!?

microsoft.public.sqlserver.tools microsoft.public.sqlserver.tools


Discuss No trace of maintenance plan checkdb in sql server error log?!? in the microsoft.public.sqlserver.tools forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Pedja
 
Posts: n/a

Default No trace of maintenance plan checkdb in sql server error log?!? - 01-05-2009 , 03:35 PM






Hi,

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?

Thanks

Reply With Quote
  #2  
Old   
Erland Sommarskog
 
Posts: n/a

Default Re: No trace of maintenance plan checkdb in sql server error log?!? - 01-05-2009 , 04:36 PM






Pedja (Pedja (AT) discussions (DOT) microsoft.com) writes:
Quote:
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, esquel (AT) sommarskog (DOT) 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/prodinf...ons/books.mspx



Reply With Quote
  #3  
Old   
Pedja
 
Posts: n/a

Default Re: No trace of maintenance plan checkdb in sql server error log?! - 01-05-2009 , 04:58 PM



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)

Thanks


"Erland Sommarskog" wrote:

Quote:
Pedja (Pedja (AT) discussions (DOT) 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, esquel (AT) sommarskog (DOT) 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/prodinf...ons/books.mspx



Reply With Quote
  #4  
Old   
Erland Sommarskog
 
Posts: n/a

Default Re: No trace of maintenance plan checkdb in sql server error log?! - 01-06-2009 , 04:14 AM



Pedja (Pedja (AT) discussions (DOT) microsoft.com) writes:
Quote:
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.


--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) 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/prodinf...ons/books.mspx



Reply With Quote
  #5  
Old   
Aaron Bertrand [SQL Server MVP]
 
Posts: n/a

Default Re: No trace of maintenance plan checkdb in sql server error log?! - 01-08-2009 , 09:46 AM



He may have been wrong, or he may have been saying that SP3 was installed on
the client (not the server)...


On 1/6/09 5:14 AM, in article Xns9B8B7270936FFYazorman (AT) 127 (DOT) 0.0.1, "Erland
Sommarskog" <esquel (AT) sommarskog (DOT) se> wrote:

Quote:
Pedja (Pedja (AT) discussions (DOT) 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.



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.