Freigeben über

Released: System Center Management Pack for SQL Server (7.0.0.0)

  • Artikel

We are happy to announce that updates to SQL Server Management Packs have been released!

Downloads available:

Microsoft System Center Management Pack for SQL Server 2016 Microsoft System Center Management Pack for SQL Server 2014 Microsoft System Center Management Pack for SQL Server (2008-2012) Microsoft System Center Management Pack for SQL Server Dashboards

Please see below for the new features and improvements. Most of them are based on your feedback. More detailed information can be found in guides that can be downloaded from the links above.

New SQL Server 2008-2012 MP Features and Fixes

  • The version of the management packs was significantly increased as the SQL Server MP product family was extended with brand new management packs for SQL Server 2017+ and SQL Server 2017+ Replication. The new management packs are designed to monitor SQL Server 2017 and the upcoming versions.
  • Reimplemented Always On workflows to enable monitoring of Availability Groups hosting over 200 databases
  • Updated alert descriptions of Availability Group monitors: added cluster name and primary replica name
  • Implemented 3 alerting rules for events #5105 (error with physical file access), #833 (IO request has taken longer than 15 seconds), and #41144 (AO availability group failed); they are disabled by default
  • Added debug information to Always On monitoring scripts
  • Disabled the alerting rule for event #18456 by default
  • Fixed issue: Invalid encoding of SQL names in Always On console tasks
  • Fixed issue: Invalid encoding of SQL instance names in Always On console tasks

 New SQL Server 2014 MP Features and Fixes

  • The version of the management packs was significantly increased as the SQL Server MP product family was extended with brand new management packs for SQL Server 2017+ and SQL Server 2017+ Replication. The new management packs are designed to monitor SQL Server 2017 and the upcoming versions.
  • Reimplemented Always On workflows to enable monitoring of Availability Groups hosting over 200 databases
  • Updated alert descriptions of Availability Group monitors: added cluster name and primary replica name
  • Implemented 3 alerting rules for events #5105 (error with physical file access), #833 (IO request has taken longer than 15 seconds), and #41144 (AO availability group failed); they are disabled by default
  • Implemented "MSSQL 2014/16: HTTP Storage: Avg. Bytes/Transfer" performance rule
  • Added debug information to Always On monitoring scripts
  • Disabled the alerting rule for event #18456 by default
  • Fixed issue: Invalid encoding of SQL names in Always On console tasks
  • Fixed issue: Invalid encoding of SQL instance names in Always On console tasks 

New SQL Server 2016 MP Features and Fixes

  • The version of the management packs was significantly increased as the SQL Server MP product family was extended with brand new management packs for SQL Server 2017+ and SQL Server 2017+ Replication. The new management packs are designed to monitor SQL Server 2017 and the upcoming versions.
  • Reimplemented Always On workflows to enable monitoring of Availability Groups hosting over 200 databases
  • Updated alert descriptions of Availability Group monitors: added cluster name and primary replica name
  • Implemented 3 alerting rules for events #5105 (error with physical file access), #833 (IO request has taken longer than 15 seconds), and #41144 (AO availability group failed); they are disabled by default
  • Added debug information to Always On monitoring scripts
  • Implemented "MSSQL 2014/16: HTTP Storage: Avg. Bytes/Transfer" performance rule
  • Enabled Memory-Optimized workflows for all editions of SQL Server 2016 by default, so far as all editions now support Memory-Optimized Data since SP1
  • Disabled the alerting rule for event #18456 by default
  • Optimized ProbeAction for User Resource Pool Memory workflows
  • Fixed issue: Invalid encoding of SQL names in Always On console tasks
  • Fixed issue: "XTP Configuration" monitor is in healthy state when XTP filegroup container and the transaction log are placed on different volumes of a physical disk
  • Fixed issue: Incorrect publishers’ names for SSIS EventCollection rules (SQL2016)
  • Fixed issue: GetSQL2016DBEngineWinServState.js crashes when getting neither "true" nor "false" as the second parameter (CheckStartupType)
  • Fixed issue: Invalid encoding of SQL instance names in Always On console tasks
  • Fixed issue: XTP Configuration monitor is always in Warning state for SQL Server 2016 Standard edition 

SQL Server Dashboards MP

  • No changes introduced; increased the version number to 7.0.0.0 to comply with the current version of SQL Server Management Packs

We are looking forward to hearing your feedback.

Comments

  • Anonymous
    November 14, 2017
    This is the link to the SQL 2017 MP: https://www.microsoft.com/en-us/download/details.aspx?id=56203&WT.mc_id=rss_windows_allproducts
  • Anonymous
    November 24, 2017
    There appears to be a bug in the Microsoft.SQLServer.2016.AlwaysOn.Discovery management pack when used with Server Core. The management pack's PowerShell scripts assume that an Microsoft.SqlServer.Management.Smo.Server object can be created ($server = New-Object Microsoft.SqlServer.Management.Smo.Server($serverConnection)), but this requires that Microsoft.SqlServer.Smo.dll be loaded. On full Server, this DLL is automatically loaded, but on Server Core (presumably because SSMS isn't installed), although this DLL is available, it isn't automatically loaded, and so the object creation fails. As a result, the Always On discoveries fail. Could this please be investigated?
    • Anonymous
      November 24, 2017
      Hi Gary, thank you for such a valuable comment. We'll have a look and get right back to you with the results.
    • Anonymous
      November 30, 2017
      I think I have the same issue, but we do not run Server Core.Error in ModuleAction Module: DatabaseReplicaAlwaysOnDiscovery.ps1 Version: 7.0.0.0:Reason: Cannot find type [Microsoft.SqlServer.Management.Smo.Server]: verify that the assembly containing this type is loaded. Position:82 Offset:13 Instance:MSSQLSERVER
      • Anonymous
        December 07, 2017
        Hi Remco, thank you for giving us your feedback. We're already working on the solution and will present it soon. Could you email us at sqlmpsfeedback@microsoft.com so that we can contact you about the solution?
        • Anonymous
          December 11, 2017
          I was out of the Office. I have sent you an e-mail with details.
    • Anonymous
      December 07, 2017
      Gary, could you email us at sqlmpsfeedback@microsoft.com? We'd like to talk about a solution for the problem.
  • Anonymous
    November 27, 2017
    Are there no changes from the preview of this MP?
    • Anonymous
      November 27, 2017
      The comment has been removed
      • Anonymous
        November 27, 2017
        Ok, when I tried to install the packs from the download link I got the message that the same version is already installed so I guess I have to remove the preview the install these ones since they both use 7.0.0.0 as version number.
        • Anonymous
          November 27, 2017
          The preview version had number 6.7.34.0, then we released RTM with number 7.0.0.0. If you already have 7.0.0.0 installed in your SCOM, you don’t need to update it. Our releases never share the same version number.Do all the SQL MPs have version 7.0.0.0 in your SCOM at the moment?
  • Anonymous
    November 28, 2017
    I'm also having troubble with AlwaysOnDiscovery, but on Full windows.It doesn't seem to load the right dll's for DatabaseReplicaAlwaysOnDiscovery.ps1 to work.If i run the functions manually the 7.0.0.0 only tries to import this:C:\Program Files (x86)\Microsoft SQL Server\130\Tools\PowerShell\Modules\SQLPS\Microsoft.SqlServer.Management.PSProvider.dllBut if i use the 6.7.31.0 it loads:C:\Program Files (x86)\Microsoft SQL Server\130\Tools\PowerShell\Modules\SQLPS\Microsoft.SqlServer.Management.PSProvider.dllC:\Program Files (x86)\Microsoft SQL Server\130\Tools\PowerShell\Modules\SQLPS\Microsoft.SqlServer.Management.PSSnapins.dll
  • Anonymous
    January 08, 2018
    The comment has been removed
    • Anonymous
      January 09, 2018
      The comment has been removed
      • Anonymous
        January 09, 2018
        Hello Alex,Thanks for the reply.You mean below rules/monitors? for each SQL DB Engine version?MONITOR: CPU utilization (%)MONITOR: Thread CountRULE: MSSQL 2016: DB Engine CPU Utilization (%)RULE: MSSQL 2016: DB Engine Thread Count
        • Anonymous
          January 09, 2018
          Hi! Yes, you're correct. At least, you need to increase the interval for only those servers where you have the errors.
          • Anonymous
            January 09, 2018
            sure Alex, thanks for the confirmation.
  • Anonymous
    January 09, 2018
    I have multiple customers facing Out of memory alert issues with latest SQL MP (similar to https://social.technet.microsoft.com/Forums/lync/en-US/03c5b2e5-efdb-4e9b-bf98-8f86f93ec2c2/mssql-monitoring-failed-with-event-id-4001-out-of-memory?forum=operationsmanagermgmtpacks)Computer: Reason: Out of memory Position:133 Offset:22 Instance:Detailed error output: Out of memoryWe have tried to increase MemoryPerHost and other property to higher level but still alerts generating.Any update on how to get this issue fixed?
    • Anonymous
      January 12, 2018
      Sometimes such errors indicate a memory leak in the WMI service, sometimes they are caused by a huge number of queries to WMI. The first thing you should check out is if both Windows Server and SQL Server are up to date. Then try to define what Windows Server versions and SQL Server versions are affected by the issue. How often do those errors appear on each machine for each SQL instance during 24 hours?