Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 688
  • Last Modified:

MOM 2005 reporting suspect 2005 SQL DB

Hello I have recently installed MOM 2005 on W2k3 and I have started monitoring several SQL database servers.  They are SQL 2000 and 2005.  I have one database on a SQL 2005 box that is getting is suspect error message in MOM.  All the other databases on the server and other servers report OK. The "suspect" database seems to be working fine and running scripts like DBCC CHECKDB come clean without any errors.

The only thing I can think of is this DB was originally created in SQL 2000 and was moved to 2005.  Is it possible that a proper "upgrade" did not occur?
Do I maybe need to just reset the status?

Below is the message from MOM.

Severity:  Critical Error
Status:  New
Source:  SQL Server 2005 Database Health:MSSQLSERVER:Database(Development)
Name:  SQL Server 2005 Database Health
Description:  The database "Development" in the instance "MSSQLSERVER" is in a critical state.  The state is: Suspect.

 Any help would be appreciated!

 Thanks
0
questinc
Asked:
questinc
  • 2
1 Solution
 
LowfatspreadCommented:
Hi questinc,
what is the message number?
what compatability level is the database at?
have you check the server/database log?

Cheers!
0
 
questincAuthor Commented:

I do not have any erros in the application log on the SQL server.
The compatability version is SQL 2000
The database log does not show any obvious errors, thought it is strange that there are periods where it kept trying to start the database.  And check it for errors each time:


Thanks

John

006-07-16 04:45:05.80 spid56      Starting up database 'Development'.
2006-07-16 04:45:48.06 spid56      Starting up database 'Development'.
2006-07-16 04:45:48.37 spid56      Starting up database 'Development'.
2006-07-16 04:45:48.81 spid56      Starting up database 'Development'.
2006-07-16 04:45:49.53 spid56      Starting up database 'Development'.
2006-07-16 04:45:50.21 spid56      Starting up database 'Development'.
2006-07-16 04:45:50.67 spid56      Starting up database 'Development'.

2006-07-17 08:45:05.39 spid60      Starting up database 'Development'.
2006-07-17 08:45:05.49 spid60      CHECKDB for database 'Development' finished without errors on 2006-07-16 10:52:45.343 (local time). This is an informational message only; no user action is required.
2006-07-17 08:45:46.93 spid60      Starting up database 'Development'.
2006-07-17 08:45:47.19 spid60      CHECKDB for database 'Development' finished without errors on 2006-07-16 10:52:45.343 (local time). This is an informational message only; no user action is required.
2006-07-17 08:45:47.44 spid60      Starting up database 'Development'.
2006-07-17 08:45:47.82 spid60      CHECKDB for database 'Development' finished without errors on 2006-07-16 10:52:45.343 (local time). This is an informational message only; no user action is required.
2006-07-17 08:45:48.85 spid60      Starting up database 'Development'.
2006-07-17 08:45:49.63 spid60      CHECKDB for database 'Development' finished without errors on 2006-07-16 10:52:45.343 (local time). This is an informational message only; no user action is required.
2006-07-17 08:45:50.27 spid60      Starting up database 'Development'.
2006-07-17 08:45:50.33 spid60      CHECKDB for database 'Development' finished without errors on 2006-07-16 10:52:45.343 (local time). This is an informational message only; no user action is required.
2006-07-17 08:45:50.72 spid60      Starting up database 'Development'.
2006-07-17 08:45:50.79 spid60      CHECKDB for database 'Development' finished without errors on 2006-07-16 10:52:45.343 (local time). This is an informational message only; no user action is required.
2006-07-17 08:45:51.13 spid60      Starting up database 'Development'.
2006-07-17 08:45:51.27 spid60      CHECKDB for database 'Development' finished without errors on 2006-07-16 10:52:45.343 (local time). This is an informational message only; no user action is required.
2006-07-17 08:45:51.61 spid60      Starting up database 'Development'.
2006-07-17 08:45:51.68 spid60      CHECKDB for database 'Development' finished without errors on 2006-07-16 10:52:45.343 (local time). This is an informational message only; no user action is required.
2006-07-17 08:45:52.02 spid60      Starting up database 'Development'.
2006-07-17 08:45:52.10 spid60      CHECKDB for database 'Development' finished without errors on 2006-07-16 10:52:45.343 (local time). This is an informational message only; no user action is required.
2006-07-17 08:45:52.46 spid60      Starting up database 'Development'.
2006-07-17 08:45:52.54 spid60      CHECKDB for database 'Development' finished without errors on 2006-07-16 10:52:45.343 (local time). This is an informational message only; no user action is required.
2006-07-17 08:45:52.90 spid60      Starting up database 'Development'.
2006-07-17 08:45:52.96 spid60      CHECKDB for database 'Development' finished without errors on 2006-07-16 10:52:45.343 (local time). This is an informational message only; no user action is required.
2006-07-17 08:45:53.36 spid60      Starting up database 'Development'.
2006-07-17 08:45:53.43 spid60      CHECKDB for database 'Development' finished without errors on 2006-07-16 10:52:45.343 (local time). This is an informational message only; no user action is required.
2006-07-17 08:45:53.82 spid60      Starting up database 'Development'.
2006-07-17 08:45:53.88 spid60      CHECKDB for database 'Development' finished without errors on 2006-07-16 10:52:45.343 (local time). This is an informational message only; no user action is required.
2006-07-17 08:45:54.26 spid60      Starting up database 'Development'.
2006-07-17 08:45:54.33 spid60      CHECKDB for database 'Development' finished without errors on 2006-07-16 10:52:45.343 (local time). This is an informational message only; no user action is required.
2006-07-17 08:45:54.71 spid60      Starting up database 'Development'.
2006-07-17 08:45:54.77 spid60      CHECKDB for database 'Development' finished without errors on 2006-07-16 10:52:45.343 (local time). This is an informational message only; no user action is required.
2006-07-17 08:58:36.22 spid59      Starting up database 'Development'.

0
 
questincAuthor Commented:
I have determined the problem.  

It seems that the person that originally created the database set it to "Auto Close".  This was causing the database to start-up all the time and would also explain why it would be sometimes considered suspect by MOM.

The "Auto Close" can be found  on the database properties windows in SQL server.

Once I made this change I stopped receiving errors from MOM.
0
 
GhostModCommented:
Closed, 250 points refunded.

GhostMod
Community Support Moderator
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now