Released: System Center Management Pack for SQL Server and Dashboards (6.7.7.0)

We are happy to announce that updates to SQL Server and Dashboard 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.

Important note to the release:

To provide support for monitoring SQL Server on Windows machines having names that longer 15 symbols, we had to add additional requests to WMI and Windows registry, and this change affects security configuration in some cases. Therefore, certain essential settings might need to be applied (see below).

To monitor SQL Server Always On Availability Groups under Local System account, each node’s Local System account must also have sufficient permissions on other server nodes of the Availability Group. In case it is approved by your company security policy, you can grant such permissions by adding each computer account to the local Administrators group of each participating node. In case it is not approved, you should create a domain account for monitoring and either add it to the local Administrators group on each node or grant it with the minimal required permission set as described in “Low-privilege configurations” section of the Management Pack Guide.

New SQL Server Dashboards MP Features and Fixes

  • Improved Dashboards performance
  • Fixed issue: expanding “arrow” has low-contrast color when a health group is collapsed in Instance view (High-Contrast #2 color scheme)
  • Fixed issue: in Web console, Dashboards continuously send requests to the database
  • Fixed issue: not the first object gets selected in the object list after drill-down
  • Fixed issue: horizontal scroll position resets after refreshing the Instance view
  • Fixed issue: “No Data” message is displayed on some tiles after upgrading Dashboards management pack from version 6.7.2.0 to 6.7.4.0 or later version
  • Fixed issue: on Web console, Dashboards crash when drilling down from Datacenter view to Instance view
  • Restored the correct group order in SQL Server Summary dashboard views
  • Fixed issue: Regular\Virtual group tile will show 0 objects if user adds a new group before the previous one has been saved
  • Fixed issue: virtual group filtering for Generic Distributor does not work
  • Fixed issue: tooltips on some menus appear in unexpected places
  • Fixed issue: Web Console is crashing upon right-clicking the Hamburger menu
  • Fixed issue: button captions are cropped in some dashboard localization packs
  • Fixed issue: Instance dashboard displays data for the item that is the first in the list if no items appear after applying a filter
  • Fixed issue: the first group object is not in focus after clearing “Filter” field if there were no search results
  • Fixed issue: Summary dashboards appear to be in a strange state if one installs only Dashboards MP without SQL MPs
  • Fixed issue: Bulk Add Tiles does not trigger the refresh action
  • Fixed issue: object and alert counters of Virtual groups containing real groups display zeros
  • Fixed issue: an error appears in Web Console when using keyboard for navigation in “Add Aggregated Monitor” dialog
  • Fixed issue: unexpected scrolling behavior in the instance view when using mouse scroll
  • Fixed issue: markup of the dialog for adding classes gets broken when the scrollbars are displayed
  • Fixed issue: wrong width value of the Edit dialog
  • Fixed issue: there is no refresh action after saving the edited Virtual Group configuration
  • Fixed issue: white-screen exception when working with a dialog in Web console
  • Fixed issue: Datacenter and Instance queries fail when a special set of classes is selected

New SQL Server 2008-2012 MP Features and Fixes

  • Added support for configurations where computer host names are longer than 15 symbols
  • Added support for databases stored on SMB Shares
  • Added “Event ID” to descriptions of all the alerts generated by the alerting rules
  • Updated the visualization library
  • Removed files of SQL 2005 MP from the installer since this MP is no longer supported
  • Added 2 rules to generate alerts when there are problems with execution of the monitoring scripts: “MSSQL: Monitoring failed” and “MSSQL: Monitoring warning”
  • Added “MSSQL 20XX: Discovery warning” rules to generate alerts when there are non-critical problems with execution of the discovery scripts (warning events in the Operations Manager log)
  • Changed “MSSQL 20XX: Discovery failed” rules to generate alerts for only critical errors during executing discovery scripts
  • Improved error logging in the MP scripts
  • Made detection condition stricter for DB User Policy event-based discovery: added management group name
  • Made detection condition stricter for Script Failed alerting rule: added management group name
  • Deprecated “Run As Account does not exist on the target system, or does not have enough permissions” rule
  • Fixed issue: SQL Server 2012 Always On discoveries fail after stopping WSFC service
  • Fixed issue: “Set DB offline” task does not work when the database is in Availability Group
  • Fixed issue: user policy discovery script fails with “Invalid namespace “ROOT\Microsoft\SqlServer\ComputerManagement12” error
  • Fixed issue: Always On console task does not work
  • Fixed some issues in the scripts, which could lead to unstable work with WMI
  • Fixed error logging in a script for Blocking Sessions monitor
  • Fixed issue: CPU Usage monitor and rule did not work for SQL Server cluster instance
  • Fixed issue: connection to an SQL Server instance was not closing when the destination was wrong
  • Fixed Non-Readable Replica detection (Always On)

New SQL Server 2014-2016 MP Features and Fixes

  • Added support for configurations where computer host names are longer than 15 symbols
  • Added “Event ID” to descriptions of all the alerts generated by the alerting rules
  • Added a new overridable parameter to monitor “Stale Checkpoint File Pairs Ratio” in order to ignore databases having the number of checkpoint file pairs less than the threshold (300 by default)
  • Updated the visualization library
  • Added 2 rules to generate alerts when there are problems with execution of the monitoring scripts: “MSSQL: Monitoring failed” and “MSSQL: Monitoring warning”
  • Added “MSSQL 2016: Discovery warning” rules to generate alerts when there are non-critical problems with execution of the discovery scripts (warning events in the Operations Manager log)
  • Changed “MSSQL 2016: Discovery failed” rules to generate alerts for only critical errors during executing discovery scripts
  • Improved error logging in the MP scripts
  • Fixed issue: “Set DB offline” task does not work when the database is in Availability Group
  • Fixed issue: Always On console task does not work
  • Deprecated “Run As Account does not exist on the target system, or does not have enough permissions” rule
  • Fixed some issues in the scripts, which could lead to unstable work with WMI
  • Fixed the issue when not all available performance counters were presented at “All Performance Data” view in Memory-Optimized Data sub-folder
  • Made “Resources Pool Memory Consumption (rollup)” enabled by default
  • Disabled Memory-Optimized Data Garbage Collection Fill Factor monitor and rule by default
  • Disabled Memory-Optimized Data workflows for all SQL Server editions that do not support Memory-Optimized Data feature
  • Fixed issue: CPU Usage monitor and rule did not work for SQL Server cluster instance
  • Fixed issue: connection to an SQL Server instance was not closing when the destination was wrong
  • Fixed issue: in some cases, Set Database Online/Offline tasks did not work for databases of SQL Server cluster instance (SQL 2016 MP)
  • Made detection condition stricter for DB User Policy event-based discovery: added management group name
  • Made detection condition stricter for Script Failed alerting rule: added management group name

We are looking forward to hearing your feedback.

Let’s block ads! (Why?)

SQL Server Release Services