SQL MP updates – version


The SQL Management packs have been updated.  This is the first major release since, back in late 2015.

I will list all the SQL MP below.  Don’t import all of them unless you need each specialization.  For instance, don’t import the reporting and analysis services MP’s if you really only want alerting and monitoring for the SQL Database Engines.


The latest versions of ALL SQL MP’s and locations below, as of 7/11/2016:


SQL 2005-2012 DB Engine

SQL 2008 Replication

SQL 2008 Reporting Services

SQL 2008 Analysis Services

SQL 2012 Replication

SQL 2012 Reporting Services

SQL 2012 Analysis Services

SQL 2014 DB Engine

SQL 2014 Replication

SQL 2014 Reporting Services

SQL 2014 Analysis Services

SQL 2016 DB Engine

SQL 2016 Replication

SQL 2016 Reporting Services

SQL 2016 Analysis Services


Comments (24)

  1. Thanks Kevin for sharing this Nice SQL Overview of MP 🙂

  2. John_Curtiss says:

    I eagerly await your (inevitable?) follow-up post enumerating the MP’s bugs. It’s a race between you and Marnix to find them all for us! On your marks, get set, go! 😉

    1. Kevin Holman says:

      Curtiss – I have to be honest, I rarely find the bugs, I often depend on customers and blog readers to report them to me, but then I investigate them and pursue the fixes for sure. I have been testing this MP in my environment for a couple weeks now, and so far, I am not seeing any major issues. However, most of the complaints come from large enterprise customers with Dashboard issues in the previously updated MP’s. I am keening interested in seeing how the fixes they put in these MP’s work for that.

      1. Stephen says:

        Still a very valuable service Kevin! The community is very appreciative of your contributions.

    1. Kevin Holman says:

      There isn’t enough info to go on there. And I would not say there is “no fix”. The customer needs to open a support case and they will attempt a repro of the specific customer environment, generally find any issue, and offer a workaround script in the meantime if possible. They also have to validate tons of invalid cluster configurations, unsupported scenarios, customer DNS issues, etc, etc.

      1. igor says:

        Yea, Microsoft currently investigating that issue ..

        1. afzal says:

          any solutions/updates

  3. Maurice Blok says:

    Thanks for putting them together in one list Kevin!

  4. M.Mathew says:

    Noticed ” MSSQL 2014: Discovery Failed” Alerts show up, after importing the new MP.Did anyone else have these issues ? Similar issues have been reported here, under comments section:


    1. Aengus says:

      Yes, and it is occurring where we had 4 boxes that originally had 2014 installed which was subsequently removed and SQL 2012 was installed instead.
      We have some debug info/found where the issue is in the script … am not sure how to get that info back to the relevant team.

      1. Aengus says:

        Sorry, just re-read your comment, in our case it is the 2012 discovery that is failing where the box previously had 2014 but now has 2012, so possibly not the same issue as yours.

      1. Aengus says:

        Follow up for others …
        In our SQL Discovery failure case, we had a version installed that was subsequently replaced by lower version leaving a empty/corrupted wmi entry:
        Get-WmiObject -Namespace root\Microsoft\SqlServer -Query “select name from __namespace where name like ‘computermanagement%’
        returned computermanagement11 and computermanagement12 in our case and the properties for computermanagement12 (SQL2014) were empty causing a provider load failure.
        We removed the empty entry with
        Get-WmiObject -Namespace root\Microsoft\SqlServer -Class __Namespace -filter “name = ‘computermanagement_put your number in here_'” |rwmi
        and discovery worked on next run.
        Note do at your own risk etc
        Thanks to my colleague Simon and Alex at Microsoft for resolving.

    2. Esben Frandsen says:

      Yes we see that too

  5. Werner says:

    I posted a question on the Operations Manager Forum about the SQL Management pack for 2014
    SQL jobs being only configured a 2 state monitor but the Default settings alerting on a Critical State only which is not in the 2 state but a 3 state monitor.

    and i see it still exists in the new Management Pack but the Dasboards finally work for me Yea

    1. Kevin Holman says:

      Technically – this is not a bug. There is no alert configuration set in the monitor, because the monitor is not designed to create alerts by default. So SCOM simply defaults to this configuration when no config is set. It is assumed when the customer changes a default setting for the monitor, such as enabling alerting where it is not enabled by default, then they would set the other appropriate settings per their operational needs.

  6. segmilne says:

    This management pack generates errors for SQL 2008/R2/2012 databases whose data files are on SMB shares. I posted more information on this error and received a response on the SQL Server Release Services blog post:


  7. Chris McIntyre says:

    Just a heads up to everybody that apparently these do not support Windows Server 2003. That’s what I’ve been told by Alex Protsenko in the comments on the release blog. Don’t see any mention of that in the documentation. If this is true I’ll have to go to the business with my tail between my legs.

    1. Kevin Holman says:

      Interesting – what specifically isn’t supported on WS2003? Is there a specific workflow that doesn’t work?

      Granted – WS2003 extended support phase ended in July 2015, so the OS is no longer supported in general. I am not surprised that newer MP’s will only be tested on supported OS platforms.

      1. Hi.

        I have a doubt. Could you please give me your idea ?

        I have a mixed environment and there is a SQL 2005 Instance on a Windows 2003 Cluster.
        Other instances are SQL 2008 / 2012 on Windows server 2008 / 2012.

        I could skip the update of the MP for SQL Server 2005 but there are the basic MP common for all SQL versions. (Core Library, Generic Dashboard, etc …)

        What happens if I will update the MP for SQL 2008 / 2012 ?
        The basic MP will be updated; so MP for SQL Server 2005 will be involved.
        I could lost monitoring for SQL installed on Win 2003.

        I’m not able to test in a lab environment, so I try to share my doubts with you.

        What you think about that ?

        Thank you.

      2. Chris McIntyre says:

        There are a couple of things failing, including a discovery:

        Management Group: MyMG. Script: DiscoverSQL2005DB.vbs. Version: Instance: MSSQLSERVER : SQL Database discovery script ‘DiscoverSQL2005DB.vbs’ for instance ‘MSSQLSERVER’ failed.
        The next errors occured:
        Cannot connect to the target Sql Server instance. Connection log:
        Connection to data source ‘server’ failed: Provider is not specified and there is no designated default provider.
        Connection to data source ‘server,1433’ failed: Provider is not specified and there is no designated default provider.


        Here is the response from Alex:
        As you know, Windows Server 2003 reached the end of extended support last year. All further releases published after the end date weren’t tested on Windows Server 2003. We had to make it obvious and pointed to that fact. It’s our fault, sorry for that.

        We’ve updated the System Requirements section on the download pages. The documentation will be updated in the next release.


        So I guess I’m looking at downgrading to the prior version of the MP, or going to the business to explain I can’t monitor SQL on Server 2003 any more.

        1. Zeeshan says:

          SQL MP Version
          Run as Account already in place with SA Permission
          Alert Name:- MSSQL 2008: Discovery failed
          Alert Description :- Management Group: XXX2012. Script: DiscoverSQL2008Files.js. Version: Instance: MSSQLSERVER : File Discovery script ‘DiscoverSQL2008Files.js’ for instance ‘MSSQLSERVER’ failed.
          Inner exception:
          Error Number :
          Error Code : 0
          Win32 Facility : 0
          Error Description :
          Call stack:Exception.constructor(File Discovery script ‘DiscoverSQL2008Files.js’ for instance ‘MSSQLSERVER’ failed.,Can’t execute query ‘SELECT database_id, name FROM sys.databases WHERE state = 0 AND source_database_id is null AND collation_name is not null AND (is_in_standby = 0 OR is_read_only = 1) AND user_access != 1 AND name NOT IN (”) ‘: [Microsoft][SQL Server Native Client 10.0][SQL Server]The SELECT permission was denied on the object ‘databases’, database ‘mssqlsystemresource’, schema ‘sys’.

          When we manully execute the query it works fine on sql.server but still the discovery is failing
          Need help

Skip to main content