Поделиться через

Released: System Center Management Pack for SQL Server, Replication, AS, RS, Dashboards (6.7.31.0)

  • Статья

We are happy to announce new updates to SQL Server Management Pack family!

  • Microsoft System Center Management Pack for SQL Server enables the discovery and monitoring of SQL Server Database Engines, Databases, SQL Server Agents, and other related components.

Microsoft System Center Management Pack for SQL Server

Microsoft System Center Management Pack for SQL Server 2014

Microsoft System Center Management Pack for SQL Server 2016

  • Microsoft System Center Management Pack for SQL Server Replication enables the monitoring of Replication as set of technologies for copying and distributing data and database objects from one database to another and then synchronizing between databases to maintain consistency.

Microsoft System Center Management Pack for SQL Server 2008 Replication

Microsoft System Center Management Pack for SQL Server 2012 Replication

Microsoft System Center Management Pack for SQL Server 2014 Replication

Microsoft System Center Management Pack for SQL Server 2016 Replication

  • Management Pack for SQL Server Analysis Services enables the monitoring of Instances, Databases and Partitions.

Microsoft System Center Management Pack for SQL Server 2008 Analysis Services

Microsoft System Center Management Pack for SQL Server 2012 Analysis Services

Microsoft System Center Management Pack for SQL Server 2014 Analysis Services

Microsoft System Center Management Pack for SQL Server 2016 Analysis Services

  • Management Pack for SQL Server Reporting Services (Native Mode) enables the monitoring of Instances and Deployments.

Microsoft System Center Management Pack for SQL Server 2008 Reporting Services (Native Mode)

Microsoft System Center Management Pack for SQL Server 2012 Reporting Services (Native Mode)

Microsoft System Center Management Pack for SQL Server 2014 Reporting Services (Native Mode)

Microsoft System Center Management Pack for SQL Server 2016 Reporting Services (Native Mode)

  • Management Pack for SQL Server Dashboards

Microsoft System Center Management Pack for SQL Server Dashboards

Please see below for the new features and improvements. More detailed information can be found in guides that can be downloaded from the links above.

Important Notes About This Release

  • Please note that we implemented a new alerting rule for SQL Server event #18456 "Login failed" in this release. However, this rule may become rather noisy due to the fact that the target events appear quite frequently in some environments. The rule is enabled by default; thus, if it creates too many alerts in your environment, consider disabling it via the override. The ideal would be to resolve the underlying issues causing the alert but we understand this is not always a priority.
  • We are introducing a new monitor in this release (see the first bullet below) based on customer feedback. You have now a better solution for monitoring backups of AG databases.

New SQL Server 2008-2016 MP Features and Fixes (6.7.31.0)

  • Added new "Availability Database Backup Status" monitor in Availability Group to check the existence and age of the availability database backups (this monitor is disabled by default)
  • "Database Backup Status" monitor has been changed to return only "Healthy" state for the databases that are Always On replicas, since availability database backups are now watched by the dedicated monitor
  • Improved performance of DB Space monitoring workflows
  • Added new "Login failed" alerting rule for SQL Server event #18456
  • Fixed issue: "Active Alerts" view does not show all alerts
  • Fixed issue: DB space monitoring scripts fail with "Cannot connect to database" error.
  • Fixed issue: PowerShell scripts fail with "Cannot process argument because the value of argument 'obj' is null" error
  • Fixed issue: Alert description of "Disk Ready Latency" and "Disk Write Latency" monitors displays the sample count instead of the performance value that was measured
  • Fixed issue: Different file location info from "sys.master_files" and "sysfiles" causes error when Availability Group secondary database files are in different path
  • Fixed issue: "DB Transaction Log Free Space Total" rules return wrong data
  • Introduced minor updates to the display strings
  • Deprecated "Garbage Collection" monitor and the appropriate performance rule
  • Resource Pool Discovery is disabled by default for pools not containing databases with Memory-Optimized Tables
  • "XTP Configuration" monitor now supports different file path types (not only those starting with C:, D:, etc.)
  • Fixed issue: "Resource Pool State" view shows incorrect set of objects
  • Fixed issue: Invalid group discovery in SQL Server 2016 Always On
  • Updated the visualization library

New SQL Server 2008-2016 Replication MP Features and Fixes (6.7.31.0)

  • Added Distributor name caching to Subscription discovery
  • Restricted the length of some string class properties
  • Improved the internal structure of SQL scripts storage
  • Fixed variable types in SQL scripts
  • Fixed connectivity issues in SmartConnect module
  • Introduced minor updates to the display strings
  • Updated the visualization library

New SQL Server 2008-2016 Reporting Services MP Features and Fixes (6.7.31.0)

  • Reimplemented Instance seed discovery: replaced the managed module with a PowerShell script
  • Reimplemented Deployment seed discovery: added a retry policy and improved error handling
  • Updated the visualization library

New SQL Server 2008-2016 Analysis Services MP Features and Fixes (6.7.31.0)

  • Restricted length of some string class properties
  • Updated the visualization library

New SQL Server Dashboards MP Features and Fixes (6.7.31.0)

  • Increased the version number to comply with the current version of SQL Server MPs

We are looking forward to hearing your feedback. This release is in English only. If you are an international customer looking for a localized version of this release, we would like to hear from you at sqlmpsfeedback@microsoft.com.

Comments

  • Anonymous
    August 22, 2017
    The alert description for the SQL Job Last Run State is empty? Can this be added again?
    • Anonymous
      August 25, 2017
      Mark, thank you for reaching out to us. This monitor has been initially introduced with "Generates Alert" property set to false. In SCOM, it means that even when you set this parameter to true, monitor's alerts will not have a description. We have got a work item in our product backlog to add the description but I can't tell you exactly when we release this improvement.
      • Anonymous
        August 30, 2017
        Hi Alex, thank you for picking it up. I understand there are might be different priorities.
      • Anonymous
        August 30, 2017
        By the way, is there another way to get these suggestions/bugs to you? Connect/Github/Uservoice? I might collect some votes ;)
        • Anonymous
          August 31, 2017
          Unfortunately we are not using any of those services at the moment. Please continue to reach out to us here.
  • Anonymous
    September 04, 2017
    Hi We have an Always On Failover Cluster installation of SQL 2016 Standard Edition and are monitoring it with SCOM and the SQLServer2016MP v6.7.31.0. We have implemented the SQL Run As account as described in this article "https://blogs.msdn.microsoft.com/tysonpaul/2016/04/09/sql-run-as-account-configuration-for-scom-made-easy", but we get the alerts listed below. Do anyone have an idea why and how to solve these problems?1. MSSQL 2016: Monitoring warningEvent ID: 4211. Management Group: ourgroup. Script: GetSQL2016DBFreeSpace.vbs. Version: 6.7.31.0 : The next errors occurred:Cannot get target instance machine's NetBios host name.Computer name: POSSQL01.ourdomain.localError number: 70Error description:Permission denied2. MSSQL 2016: Monitoring failedEvent ID: 4211. Management Group: Ourgroup. Script: ModuleAction Module: StolenServerMemory2016DataSource.ps1 Version: 6.7.31.0 : Error occurred during SQL 2016 Stolen Server Memory data source executing.Computer:POSSQL01.ourdomain.local Reason: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) Position:131 Offset:22 Instance:MSSQLSERVERDetailed error output: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))--------Requested registry access is not allowed.--------Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))3. MSSQL 2016: Discovery failedEvent ID: 7105. Management Group: Ourgroup. Script: DiscoverSQL2016MirroredDB.vbs. Version: 6.7.31.0. Instance: MSSQLSERVER : Mirrored DB discovery script 'DiscoverSQL2016MirroredDB.vbs' for instance 'MSSQLSERVER' failed.The next errors occurred:Cannot get target instance machine's NetBios host name.Computer name: POSSQL01.ourdomain.localError number: 70Error description:Permission deniedBest RegardsFrederick
    • Anonymous
      September 05, 2017
      The comment has been removed
  • Anonymous
    September 12, 2017
    Hi DmitriyThanks for your reply. It helped a lot, all 3 alerts have closed and the SQLServer2016MP v6.7.31.0 reports that every things is healthy on our SQL cluster :-)Best RegardsFrederick
  • Anonymous
    September 27, 2017
    I'm running into something since updating to 6.7.30 versions of the SQL DBE/SSRS/SSAS MPs (from 6.7.15) where I'm seeing alerts related to the SQL RunAs account. Specifically upon installation I received alerts that the RA account was not distributed to my OM MS and GW boxes (~10 in all). There is no reason the account should be distributed to these that I'm aware of - never have prior and I didn't see anything in the docs indicating there was a change that would impact this. To try and address this I distributed the RA account to these boxes and now I'm seeing the predicable "Run As Account Could Not Log On" alert since the RA account isn't granted any sort of access on MS or GW boxes.Is this a bug by any chance or was there a change that would explain this?
    • Anonymous
      November 15, 2017
      Hello, Can you email us at sqlmpsfeedback@microsoft.com with details of the problem, please?