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

[アーティクル]
06/30/2016

We are happy to announce that Management Packs to monitor SQL Server 2016 product family and updates to existing Management Packs have been released! Only the English versions are available at this time. Localized Management Packs will be made available later this summer.

Downloads available:

Please see below for the new features and improvements. Most of them are based on your feedback. Some highlights:

Much improved dashboard performance
Long asked for support for SQL Express instances
Support for TLS 1.2 in connection logic
Improved behavior around Always On scenarios

More detailed information can be found in guides that can be downloaded from the links above.

New SQL Server Dashboards MP Features and Fixes

Improved Dashboards performance
Added a feature to support Virtual Groups (groups defined by classes, not by real group instance). This will help users with partial access to use our predefined dashboards.
Added a feature to Bulk Add tiles from the class definition.
Added a feature to ignore some states while calculating the worst state for the Datacenter View State Tile; added a feature to set this ignorance up for each group
Added a feature to show/hide Instance path in the list on the Instance view
Added instance path to the Instance Details
Implemented deferred loading of the instance tiles to make the instance view operation faster
Implemented a new format for Dashboards configuration providing a smaller size and a single binding
Implemented a converter from old to new format providing preservation of user changes
Improved error reporting
Improved performance of initial load process
Improved data sources performance
Improved performance of instance selection (made it asynchronous)
Improved performance of Datacenter and Instance View Tiles, loading and loaded animations
Fixed animation issues and minor visual glitches (positioning, size of elements, fonts, main loading animation)
Updated Summary dashboard
“Known issues and Troubleshooting” section of the guide is updated

New SQL Server 2005-2012 MP Features and Fixes

Added rules for alerting when an Availability Replica changed its role and/or a Database Replica changed its role
Created a group for WOW64 SQL Server instances and disabled launching of some workflows for these instances
Added MP version line into MP events generated by the scripts
Fixed the display strings and Knowledge Base articles
Fixed issue: some scripts were not returning data when one of the few installed instances was stopped
Fixed issue: SPN configuration monitor used stale data
Fixed issue: mirroring monitoring scripts were failing when the instance was stopped
Fixed Always On Database replica discovery incorrect behavior; fixed Always On policies discovery and monitoring
Fixed Database policies discovery and monitoring
Fixed and optimized CPU Usage monitoring scripts (the issue appeared when only one core was assigned)
Added support for more than 32 processors count in CPU Usage monitoring.
SQLPS module is now used for the tasks instead of deprecated SQLPS.EXE
Implemented FILESTREAM filegroup monitoring
Multiple Ports are now supported in SQL Server TCP/IP parameters
Fixed error occurring when no port is specified in SQL Server TCP/IP parameters
Fixed filegroup read-only state discovery
Fixed RunAs profiles mapping for some workflows
Implemented support for TLS 1.2 in connection logic
Implemented support for different client drivers in connection logic
Updated connection logic error logging
Added RunAs profiles for mirroring monitors, fixed mirroring discovery issues
Fixed issue: CPU usage monitor ignored SQL server limitations on CPU core count
Fixed display strings and Knowledge Base articles
Fixed error reporting in the scripts
Fixed intermittent "Cannot login to database" alert with some rules
Added support for SQL Express Instances
Updated Knowledge Base articles
Microsoft SQL Server 2012 x86 on Windows 2008 R2: fixed the issue when DB file groups cannot be discovered
Win10 support: fixed "Cannot bind argument to parameter 'Path' because it is an empty string." issue
Fixed issue when SQL Configuration Manager starts snap-in of wrong version
Fixed invalid Always On non-readable replica detection

New SQL Server 2014-2016 MP Features and Fixes

Added rules for alerting when an Availability Replica changed its role and/or a Database Replica changed its role
Added MP version line into MP's events generated by the scripts
Fixed issue: some scripts were not returning data when one of the few installed instances was stopped
Fixed issue: SPN configuration monitor used stale data
Fixed: mirroring monitoring scripts were failing when the instance was stopped
Fixed Smart Admin policies monitoring
Fixed Always On Database replica discovery incorrect behavior; fixed Always On policies discovery and monitoring
Fixed Database policies discovery and monitoring
Fixed and optimized CPU Usage monitoring scripts (the issue appeared when only one core was assigned)
Added support for more than 32 processors count in CPU Usage monitoring.
SQLPS module is now used for the tasks instead of deprecated SQLPS.EXE
Implemented FILESTREAM filegroup monitoring
FILESTREAM is now supported on the summary dashboard
Multiple Ports are now supported in SQL Server TCP/IP parameters
Fixed error occurring when no port is specified in SQL Server TCP/IP parameters
Fixed filegroup read-only state discovery
Fixed RunAs profiles mapping for some workflows
Implemented support for TLS 1.2 in connection logic
Implemented support for different client drivers in connection logic
Updated connection logic error logging
Updated SMO usage in Always On workflows to support the new connection logic
Fixed issue: CPU usage monitor ignored SQL server limitations on CPU core count
Fixed display strings and Knowledge Base articles
Fixed error reporting in the scripts
Fixed intermittent "Cannot login to database" alert with some rules
Fixed display string for AgentsGroup.Discovery
Added support of SQL Server Express Instances
Always On issue: Events “967” are no longer fired for File Group and Files discoveries when server has a non-readable DB
DB Discovery issue fixed: masterDB is to be used if the target is inaccessible
DBSize issue: filter < 0 values in provider, return data for fileSize
Win10 support: fixed "Cannot bind argument to parameter 'Path' because it is an empty string." issue
Agent Job Discovery is now disabled by default
Fixed issue when SQL Configuration Manager starts snap-in of wrong version
Fixed invalid Always On non-readable replica detection
Updated the visualization library
Updated summary dashboards

New SQL Server 2014 MP Features and Fixes

Created a group for WOW64 SQL Server instances and disabled launching of some workflows for these instances
Changed implementation of Memory-Optimized Data free space calculation
Added Memory-Optimized Data Stale Checkpoint File Pairs Ratio Monitor

New SQL Server 2016 MP Features and Fixes

Changed EventID for MP events generated by the scripts (became 4202 for the Always On scripts and 4211 for the others)
Disabled Memory-Optimized Data workflows for SQL Server 2016 Express
Added new performance rules for Always On Log Apply Pending/Ready Queue counters
Added support for new SQL Server 2016 Memory-Optimized Data implementation
Run As profiles are now presented in GPMP library and ready to become generic profiles for all SQL Server MPs starting with 2016
Updated Availability Group Automatic Failover monitor
Added rules to collect new Always On performance counters
Upgraded the used PowerShell version to 3+, since SQL Server 2016 uses .Net 4 Runtime

New Replication 2008-2016 MP Features and Fixes

Fixed percentage threshold comparison of deactivated subscriptions workflow in Distributor
Added support for SQL Express edition
Added timeout support for .Net modules
Reviewed threading implementation
Supported case-sensitive collation on DBEngine instance
Updated Low-Privilege Environments configuration
Updated Known Issues and Troubleshooting section of the guide
Updated dashboards to support SQL Server 2016 Replication objects
Decreased database timeout value for some workflows to match new connection logic
Fixed issue: Distributor Discovery could fail for Replication
Fixed error logging, added more details
Fixed "Availability of the Distribution database" monitor issue: added missing overridable parameter
Fixed replication monitoring issue: compatibility with SQL 2005 as a part of Replication
Fixed Publisher Discovery issue: unable to cast object of type 'System.DBNull' to type 'System.String'
Fixed issue: SQL Server Event Log Collection Target was not discovered Associate due to invalid path in DataSource
Fixed issue: an INSERT EXEC statement cannot be nested
Fixed Replication Agent State monitor type cookdown issue
Fixed issue: failing replacement warning in "One or more of the Replication Agents are retrying on the Distributor" monitor
Assigned SDK profile to the Replication Database Health Discovery
Fixed upgradeability
Fixed Knowledge Base articles and display strings
Fixed "Invalid length parameter passed to the LEFT or SUBSTRING function" error after deleting last replication objects
Fixed “SQL Server blocked access to Agent XP's procedure”
Updated the visualization library

New Analysis Services 2016 MP Features and Fixes

Updated references and removed deprecated elements to support 6.6.4.0+ visualization library
Fixed bug when SSAS Monitoring Pack could not collect OS performance counters with localized names
Updated discoveries to throw errors in case of some problems detected during the discovery
Fixed module error collection on cluster instances to reduce the noise
Changed defaults for CPU Usage monitor, added sampling to Memory Usage on the server monitor
Reduced inner complexity of modules
Fixed the discoveries; now the last items can be undiscovered
Simplified the dashboard to make it quicker and more informative
Reviewed and updated the Knowledge Bases
Added timeout support for every non-native workflow
Fixed Blocking Session Monitor – in some situations it could calculate blocking sessions incorrectly
Win10 support: fixed OS version detection issue
Fixed CPU usage alert description
“Known Issues and Troubleshooting” section of the guide is updated
Updated the visualization library
Run As profiles are now presented in GPMP library and ready to become generic profiles for all SQL Server MPs starting with 2016

New Reporting Services 2016 MP Features and Fixes

Fixed issue: Microsoft System Center Management Pack for SQL Server Reporting Services doesn’t discover SSRS instance when the instance name starts from some certain symbols (0-9, A-F)
Instance configuration monitor is introduced
Implemented a better logging system
Improved the Report Manager availability monitor: now it parses human readable message to get the real status of the Report Manager
Improved the Report Manager and Web Service availability monitors: now the user can treat some status codes as healthy via the override.
Fixed the discoveries, now the last items can be undiscovered
Added timeout support for every non-native workflow
Simplified the dashboard to make it quicker and more informative
Reviewed and updated the Knowledge Base articles
Improved Run As mappings
Updated the discoveries to throw errors in case of some problems detected during the discovery
Updated the references and removed deprecated elements to support 6.6.4.0+ visualization library
Changed the performance rules write actions accounts to “Default Action account”
“Known Issues and Release Notes” section of the guide is updated
Fixed “Memory consumed by other processes (%)” rule having no Run As profile for DS; added SQL MP default Run As to the data source
Fixed “Failing replacement: $Data/Context/Property[@Name='<MonitorName>’]$” issue in OM log
Updated the visualization library
Run As profiles are now presented in GPMP library and ready to become generic profiles for all SQL Server MPs starting with 2016

We are looking forward to hearing your feedback.

Comments

Anonymous
June 30, 2016
After open a "Microsoft System Center Management Pack for SQL Server (2005-2012)" download link, it offers the version 6.7.2.0 in details, but the truly downloaded "SQLServerMP.msi" contains the version 6.6.4.0 only! When it will be refreshed?
- Anonymous
  June 30, 2016
  This might be a refresh issue with download center or some sort of caching issue. Could you try again? We are able to get to the 6.7.2.0 MSI.
  - Anonymous
    June 30, 2016
    Thanks,Now its fine, download brings the 6.7.2.0 version.
Anonymous
June 30, 2016
when I tried install Microsoft SQL Server Core Library via SCOM 2012 R2 import pack from catalog feature, after the succesful package download, the import fails with this message:"Microsoft SQL Server Core Library could not be imported.If any management packs in the Import list are dependent on this management pack, the installation of the dependent management packs will fail.Verification failed with 1 errors:-------------------------------------------------------Error 1:Found error in 2|Microsoft.SQLServer.Library|6.7.2.0|Microsoft.SQLServer.Library|| with message:Could not load management pack [ID=Microsoft.SQLServer.Generic.Presentation, KeyToken=31bf3856ad364e35, Version=6.7.2.0]. The management pack was not found in the store.: Version mismatch. The management pack ([Microsoft.SQLServer.Generic.Presentation, 31bf3856ad364e35, 6.6.7.6]) requested from the database was version 6.7.2.0 but the actual version available is 6.6.7.6."Please, actualize the version in the store also.Thanks.
- Anonymous
  June 30, 2016
  It has been updated, but refresh will take some time.
Anonymous
July 03, 2016
The comment has been removed
- Anonymous
  July 04, 2016
  Our team is investigating the issue you described. I'll keep you posted on the progress.
  - Anonymous
    August 16, 2016
    Has there been any progress on this issue, I have a few servers experiencing this?
    - Anonymous
      August 17, 2016
      Do you see errors of CPUUsagePercentDataSource.ps1 script in your cluster environments? We have fixed this issue and will present the fix in the next release which is expected to go live at the end of September. The CTP1 version (6.7.3.0) of the coming release is already available at https://www.microsoft.com/en-za/download/details.aspx?id=51645, and the fix is provided in there. If you have a chance to try the CTP1 in your test environments and make sure that the issue has gone, we will very appreciate your help.If you see errors of any other scripts, please let us know at SQLMPsfeedback@microsoft.com.
      - Anonymous
        September 13, 2016
        Any Progress on the "Discovery failed" issue?
      - Anonymous
        September 19, 2016
        Hi, Lars. Those discovery fails appeared because of running agents on Windows 2003 which is not supported now due to the life cycle end. It won't be fixed. To make sure that you didn't face with issues about which we don't know yet, please send us the details at sqlmpsfeedback@microsoft.com.
Anonymous
July 04, 2016

a lot of that errors on serversManagement Group: 123. Script: DiscoverSQL2008DB.vbs. Version: 6.7.2.0. Instance: MSSQLSERVER : SQL Database discovery script 'DiscoverSQL2008DB.vbs' for instance 'MSSQLSERVER' failed.The next errors occured:Cannot connect to the target Sql Server instance. Connection log:Connection to data source 'MSK-WSSDB1' failed: Provider is not specified and there is no designated default provider.Connection to data source 'MSK-WSSDB1,1433' failed: Provider is not specified and there is no designated default provider.

Anonymous
July 04, 2016
The comment has been removed
- Anonymous
  July 04, 2016
  Quick update - I'm not encountering this problem with the SQL 2014 management packs.
- Anonymous
  July 04, 2016
  SQL Server 2005-2012 Management Pack doesn't support monitoring for data files on SMB share. Please disable appropriate workflows for databases having files on SMB shares.
- Anonymous
  July 04, 2016
  SQL Server 2005-2012 Management Pack doesn’t support DB space monitoring for data files on SMB share. To avoid appearing those warnings, you can either turn off Autogrowth setting for the db files on SMB shares or disable appropriate workflows for that database files.
  - Anonymous
    July 05, 2016
    Thanks for the response Alex.The majority of our environment uses SMB shares given that support was added for it without enabling trace flag 1807 since SQL 2008 R2 onwards, so it's disappointing to hear that this monitoring is not supported in the management pack, and I do not see this information present in the management pack guide. Is this because of SQL 2005 compatibility? Now that this has reached end of life, ideally we have a SQL 2008-2012 management pack or split into individual versions instead. We have already observed that the SQL 2005-2012 management pack is incapable of determining free space on the underlying volume if the data files are on SMB, despite autogrowth being enabled. We have not had the script errors appear with management pack version 6.6.4.0, so we have now reverted back.
    - Anonymous
      July 13, 2016
      SQL MPs v.6.6.4.0 had some issues in DB Space monitoring. One of them was the cause why you didn't see the errors for SMB Shares. We fixed and improved error reporting to make it more useful. As a side effect, you see that errors now. I'd recommend you to use the new SQL MPs of v.6.7.2.0 because there are many fixes and improvements there. You can disable DB Space monitoring workflows for DBs stored on SMB Shares to avoid the error appearances.SMB Shares support for both SQL 2008 R2 and 2012 will be added to the next release.
      - Anonymous
        July 13, 2016
        Thanks very much Alex. We'll likely plan an upgrade to the new management packs as suggested.
    - Anonymous
      August 17, 2016
      We have released the Community Technology Preview 1 version (6.7.3.0) of the coming release. In this CTP version, SMB shares as a storage option are already supported for SQL Server 2008. I'd like to ask you to try this version in your test environments and give us your feedback if it is possible.
Anonymous
July 04, 2016
The comment has been removed
Anonymous
July 08, 2016
I am also seeing the "Cannot connect to the target Sql Server instance. Connection log:Connection to data source 'datasource' failed: Provider is not specified and there is no designated default provider."Seeing this on numerous Windows Server 2003 x64 servers. Sounds like this issue:https://support.microsoft.com/en-us/kb/971987Seeing it from the following scripts:DiscoverSQL2005DB.vbsGetSQL2005DBFileGroupFreeSpace.vbsGetSQL2005DBFreeSpace.vbsGetSQL2005DBFilesFreeSpace.vbs
- Anonymous
  July 13, 2016
  SQL MPs v. 6.7.2.0 do not support SQL Server installations on Windows Server 2003.
  - Anonymous
    July 13, 2016
    Alex, OK - Is that mentioned in the documentation anywhere? I see that 32 bit versions of SQL are not supported on 64 bit windows, but I don't see Operating System version mentioned anywhere. The low privilege instructions area of the documentation actually mentions 2003 versions specifically as needing extra settings. I'll have to go back to the business with this bit of news, wish I had known of the limitation before importing the MP.
    - Anonymous
      July 14, 2016
      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.
Anonymous
July 08, 2016
Also seeing this error on a handful of Windows Server 2003 x64 servers. May be same root cause as the issue described in my previous comment, not sure. I used wbemtest to manually open the instance of this class and look at it, so WMI itself seems to be working fine."Management Group: MyMG. Script: Main Module: CPUUsagePercentDataSource.ps1 Version: 6.7.2.0 : Error occured during CPU Usage for SQL Instances data source executing.Computer: MyComputerReason: Can not query data from Win32_ComputerSystem WMI namespace. Error persisted after 3 tries. Position:127 Offset:9Detailed error output: Can not query data from Win32_ComputerSystem WMI namespace. Error persisted after 3 tries."
- Anonymous
  July 13, 2016
  As I replied above, SQL MPs v. 6.7.2.0 do not support SQL Server installations on Windows Server 2003.
  - Anonymous
    October 27, 2016
    Does that include Windows Server 2003 R2?
    - Anonymous
      October 28, 2016
      Windows Server 2003 and 2003 R2 reached the extended support date on the same day, on July 14, 2015. Therefore SQL MPs starting with v. 6.7.2.0 do not support that OSes.
      - Anonymous
        November 17, 2016
        The comment has been removed
      - Anonymous
        November 22, 2016
        Hi Teun, I can't answer exactly under your comment because of the limit for nested messages. Probably, you used to have an instance of SQL Server 2012 or 2014 installed on that machine and then uninstalled it or them. Despite the fact that uninstalling was finished successfully, the WMI namespaces of that versions remained in WMI. It may cause the errors you have. You just need to remove the broken namespaces (they're broken since they don't include many necessary classes). To do it, use the next scripts:1. Find all namespaces: Get-WmiObject -Namespace root\Microsoft\SqlServer -Query “select name from __namespace where name like ‘computermanagement%’SQL Server 2008 and 2008 R2 namespace name is computermanagement10. SQL 2012 — computermanagement11, SQL 2014 — computermanagement12.2. Remove namespaces that are owned by non-installed versions of SQL Server: Get-WmiObject -Namespace root\Microsoft\SqlServer -Class __Namespace -filter “name = ‘computermanagement[put your number in here]'” |rwmiPlease notify us about results here or at sqlmpsfeedback@microsoft.com.

次の方法で共有

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

Comments

その他のリソース