Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

MOM 2005 reporting suspect 2005 SQL DB

Posted on 2006-07-17
5
Medium Priority
?
670 Views
Last Modified: 2012-06-27
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
Comment
Question by:questinc
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
5 Comments
 
LVL 50

Expert Comment

by:Lowfatspread
ID: 17125052
Hi questinc,
what is the message number?
what compatability level is the database at?
have you check the server/database log?

Cheers!
0
 

Author Comment

by:questinc
ID: 17125225

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
 

Author Comment

by:questinc
ID: 17146281
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
 
LVL 1

Accepted Solution

by:
GhostMod earned 0 total points
ID: 17185196
Closed, 250 points refunded.

GhostMod
Community Support Moderator
0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied? You can use SQL Server Initialize from Backup…
When trying to connect from SSMS v17.x to a SQL Server Integration Services 2016 instance or previous version, you get the error “Connecting to the Integration Services service on the computer failed with the following error: 'The specified service …
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.

636 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question