System Center Operations Manager by Jonathan Hambrook

July 2, 2007

SQL 2000 showing as ‘Not monitored’

Filed under: Microsoft, SCOM 2007 — opsmgr @ 10:13 pm

A common question asked in a lot of forums is why is SQL 2000 showing as ‘Not monitored’ even though I have the Management Pack installed.

SQL 2000 Not Monitored

Well as it says, its not being monitored. This doesn’t mean that you can’t it is simply that the rule that is used to monitor this object is currently not enabled. A quick one for all the newbies to SCOM, you aren’t just able to find the rule and click enable like in MOM 2005. However I would suggest you plan this as the design in SCOM 07 is to have you create overrides. This will require the use of a Management Pack which out of the box there is just the one that you can use which is the ‘Default Management Pack’.

Here is a quick step by step on how to enable the SQL 2000 Monitoring. Note: This can be used for any MP but SQL seems to be the most commonly asked as most of us would assume installing the MP would just work.

1. Open the Operations Manager Console and go to Authoring

2. Select Monitors under Management Pack Objects

3. To make it easy to locate the right Monitor change the scope to look at just SQL 2000 DB Engine

4. Expand Availability

SQL 2000 DB Availability

5. Right click on the SQL DB Engine Service Health Rollup and select Overrides -> Override the Monitor -> For all object type: SQL 2000 DB Engine. (You will notice that enable is greyed out, this because this MP is locked. We will be creating an override in a new MP. Also not the light greyed area in the above screen-shot, this is due to the the fact I used the search feature to find the exact Rule quickly using the word Health so each Rule with Health in it shows in Black.)

6. As per the screen shot, Tick the Override box next to Parameter you want to change and in the Override Setting change the field to the appropriate setting. For full functionality you can tick them all and if that’s too much you can scale back.

7. Select the Management Pack you would like to create this override in, I have an SQL Override Management Pack where I store all the SQL Overrides in. This I find makes it easy to track down in the feature, you are also then able to run a report against that Management Pack to get a list off the rules it contains.

SQL 2000 Override Settings

8. Click OK. In most cases you will need wait for the Agents to update but if you are impatient, just stop and restart the Health Service on the SQL 2000 server you are monitoring.

SQL 2000 DB Availablity OK


1 Comment »

  1. Thanks! I would have been scratching my head for many hours before I stumbed upon this.:)

    Your blog is a great resource.

    Comment by TG — July 13, 2007 @ 5:47 am

RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

Blog at

%d bloggers like this: