scopus69rŠn³¯g¢Êzšš,µ©bj

I recently did a new install of SCOM 2007 SP1. I noticed a none of my SQL
2000 servers are not showing the SQL 2000 DB Engine.

I found this post on Google:

"Here is the solution for this problem. The SQL 2000 state will be 'Not
Monitored' until you enable the SQL 2000 "Health Role Up" monitor via the
Authoring tab. For some reason health role up is disabled for SQL 2000 and
has a different role up structure to SQL 2005. Enabling SQL 2000 roll up
does not seem to be mentioned in the SQL Management pack guide. If ever you
see "Not Monitored" and no obvious errors are in the Operations Manager
event log then check whether the rule is enabled and if not enable via an
override."

Most of my SQL settings look enabled.

anders bengtsson [mvp]

Hi Scopus69,

I think you will have to create a override on that monitor for all your 2000
db engines, and in the override settings box configure enable = true.

Have you done that?


--
Anders Bengtsson
Microsoft MVP - Operations Manager
http://www.contoso.se

S> I recently did a new install of SCOM 2007 SP1. I noticed a none of
S> my SQL 2000 servers are not showing the SQL 2000 DB Engine.
S>
S> I found this post on Google:
S>
S> "Here is the solution for this problem. The SQL 2000 state will be
S> 'Not Monitored' until you enable the SQL 2000 "Health Role Up"
S> monitor via the Authoring tab. For some reason health role up is
S> disabled for SQL 2000 and has a different role up structure to SQL
S> 2005. Enabling SQL 2000 roll up does not seem to be mentioned in the
S> SQL Management pack guide. If ever you see "Not Monitored" and no
S> obvious errors are in the Operations Manager event log then check
S> whether the rule is enabled and if not enable via an override."
S>
S> Most of my SQL settings look enabled.
S>

scopus69rŠn³¯g¢Êzšš,µ©bj

Anders,

I did some more tweaking and I was able to get the SQL 2000 BD to show up
properly. I thibk one of them was using hte override setting to enable =
true Thanks!