locked
SQL 2012 SP1 DB Engine discovery; incorrect version RRS feed

  • General discussion

  • Hi All

    I've added the latest SQL MPs (6.4.1.0) to our SCOM 2012 R2 instance and have been working through the steps to get our 2008 and 2012 DBs added and monitored by SCOM. The 2008 db's have gone in fine, but I noticed that our 2012 db's are visible but are not monitored. 

    What I've noticed is that the "SQL Server 2012 DB Engine Group" has not been populated (unlike the 2008 engine groups) and looking at the dynamic inclusion rule, it's trying to match the wildcard 11.0.*. This is where it gets interesting, because I can see from querying the SQL server directly that each 2012 instance has a version of 11.0.3000.0, but the version under  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\110\SQLServer2012\CurrentVersion is 11.1.3000.0. The engine version that SCOM reports is also 11.1.3000.0, so I assume that it's picking up this as the version and is therefore not adding the SQL 2012 instance to the DB Engine Group because it doesn't match the 11.0.* wildcard.

    Whilst I've found one or two articles that refer to this problem (specifically http://ianblythmanagement.wordpress.com/2013/09/12/sql-server-2012-db-engine-group-problem), I can't work how to get around this problem and get these 2012 dbs monitoring in SCOM. I don't fancy attempting to change version number on the SQL servers, and I can't work out a way to amend or override the 2012 Discovery MP to also pick up 11.1.* versions.

    Does anyone have any ideas on how to work around this (other than wait for an update to the MP and hope it's fixed there !) ?

    Cheers

    Neil

    • Changed type Niki Han Monday, March 3, 2014 9:14 AM
    Wednesday, February 26, 2014 2:09 AM

All replies