Category Archives: #SQL

SCOM: Updated SSRS and SSAS management pack v7.0.17.0

Updates to SQL Server Reporting Services and Analysis Services Management Packs have been released you can get them at the below links:

SSRS
SQL Server 2008 Reporting Services (Native Mode)
SQL Server 2012 Reporting Services (Native Mode)
SQL Server 2014 Reporting Services (Native Mode)
SQL Server 2016 Reporting Services (Native Mode)
SSAS
SQL Server 2008 Analysis Services
SQL Server 2012 Analysis Services
SQL Server 2014 Analysis Services
SQL Server 2016 Analysis Services


Fixes and changes for SSRS

  • SSRS 2016: Updated monitoring of Memory Consumption and CPU Usage in order to collect performance data for all subprocesses in addition to the main SSRS service process.
  • SSRS 2016: Updated monitors “Report manager accessible” and “Web service accessible” to consider specifics in how appropriate SSRS 2016 web services work
  • Added support for cases when connection string to SSRS Database is set up the way different from “MachineName\InstanceName” (e.g., <IPAddress,Port>) and SSRS Database is in Availability Group or hosted either by named instance or SQL Cluster instance
  • Improved descriptions of events thrown by management pack to make it easier to figure out error reason
  • Improved error handling and error descriptions for cases when workflows can’t get responses from WMI
  • Improved error handling in workflows that watch for memory consumption
  • Fixed Start/Stop tasks
  • Fixed issue that caused some workflows to throw error events when SQL Server instance hosting SSRS Databases happened to stop operating or refuse connections
  • Fixed issue which caused Reporting Service instance to get undiscovered when WMI didn’t respond to calls
  • Updated display strings

Fixes and changes for SSAS

  • Added performance collections for MDX Query performance counters
  • Added retry logic to some workflows in order to reduce “Category does not exist” errors thrown when WMI fail to respond
  • Improved error handling in workflows that watch for memory consumption
  • Improved descriptions of events thrown by management pack to make it easier to figure out error reason
  • Fixed Start/Stop tasks
  • Fixed issue when “SQLServerInstalled” property was set to “False” if SQL Server DB Engine was of higher version than SSAS instance
  • Updated Dashboards configuration to show tiles for new MDX performance collections
  • Updated display strings

SCOM: SSRS2017+ MP now with Power BI Reporting v7.0.12.0

An update to SQL Server Reporting Services 2017+ Management Pack is released. This update introduces Power BI Report Server monitoring capabilities to the existing SSRS MP. It considers Power BI Report Server as a special kind of SSRS and provides the same monitoring for PBIRS instances as it does for SSRS instances.

It’s great to see new features like this, Power BI is a powerful tool.

Get it here

SCOM 1801: Updates management packs for SQL Server v7.0.7.0

New versions of the SQL MPs have been released you can get them using the links below:

SQL Server

SQL Server 2017+ –  here
SQL Server 2016here
SQL Server 2014here
SQL Server 2008-2012here

SSAS

SSAS 2016 – here
SSAS 2014 – here
SSAS 2012 – here
SSAS 2008 – here

SSRS (Native Mode)

SSRS 2016 – here
SSRS 2014 – here
SSRS 2012 – here
SSRS 2008 – here

SQL Server 2017+ MP New Features and Fixes

  • Implemented an ability to monitor SQL Server Cluster instances locally; formerly, it was possible only in Agentless and Mixed modes
  • Added the SSIS monitoring
  • Added the “Exclude List” property in DB Engine Discovery in order to filter instances, which are not subject to monitoring
  • Added the “Exclude List” property in DB Discovery in order to filter databases, which are not subject to monitoring
  • Implemented a feature: both “Exclude List” properties support usage of the asterisk character to make the filter more flexible; e.g. “*temp” is used to exclude instances/databases ending with “temp” and having anything in the beginning
  • Added the “Computers” view
  • Added the “ClusterName” property to the AG class and updated AG alerts in order to display the property within
  • Updated the “SP Compliance” monitor in order to support the Modern Servicing Model for SQL Server: the monitor will check build number instead of Service Pack number
  • Updated the “SPN Status” monitor so that it requires only a single SPN record when only TCP/IP is enabled and the instance is the default one
  • Updated the “Database Backup Status” monitor: it is disabled by default now
  • Updated the DB Space monitors so that their alert descriptions include the actual value of space available
  • Updated the “Configuration Security” section in the guide
  • Fixed issue: The “Database Health Policy” monitor ignores the “Critical” state (on Windows only)
  • Fixed issue: The “Alert severity” property of the “DB File Free Space Left” monitor has incorrect Default Value
  • Fixed issue: The “DB Filegroup Fx Container” rollup monitor has an alert parameter with a wrong value within
  • Fixed issue: “Resource Pool Memory consumption” monitor may not change its state to “Critical” for the “default” resource pool
  • Fixed issue: “Number of Samples” parameter of “Resource Pool Memory consumption” alert displays incorrect data
  • Fixed issue: Missed image resources in the SQL Server 2017+ Core Library
  • Fixed issue: “The agent is suspect. No response within last minutes” alerting rule does not catch appropriate events due to the wrong source

SQL Server 2014-2016 MP New Features and Fixes

  • Updated alert severity in some monitors
  • Updated the display strings
  • Updated the “Max worker thread count” data source of the corresponding monitor and performance rule
  • Fixed issue: In some environments, DB Space workflows fail when a secondary database is non-readable
  • Fixed issue: The “Transaction Log Free Space (%)” monitor does not work
  • Fixed issue: The “The agent is suspect. No response within last minutes” alerting rule does not catch appropriate events due to a wrong source

SQL Server 2008-2012 MP New Features and Fixes

  • Fixed issue: In some environments, DB Space workflows fail when a secondary database is non-readable
  • Fixed issue: The “The agent is suspect. No response within last minutes” alerting rule does not catch appropriate events due to a wrong source
  • Fixed issue: The “DB File Space” monitor in the SQL 2008 management pack throws error events due to the unnecessary $ character in its alert configuration
  • Updated the “Max worker thread count” data source of the corresponding monitor and performance rule
  • Fixed issue: The “Transaction Log Free Space (%)” monitor does not work

SSAS 2008-2016 MP New Features and Fixes

  • Updated the Visualization Library

SSRS 2008-2016 MP New Features and Fixes

  • Added support for cases when a connection string of the SSRS instance to the SSRS Database is not in the “MachineName\InstanceName” format; e.g., “<IP Address>, <Port Number>” or “(local)”, etc. Such connection strings are fully supported for default SQL Server instances hosting the SSRS Database. If the instance is named, workflows targeted at the SSRS Instance object work properly, but those targeted at the Deployment object cannot work, as there is no possibility to learn the FQDN of the server.
  • Updated the Deployment Seed discovery so that it does not check if the SQL Server instance hosting the SSRS Database is running
  • Updated the Visualization Library

SCOM 1801: Updated SQL Server Management Packs v7.0.4.0

New versions of the SQL server management packs are available at the following locations:

SQL Server 2008/1012 – here
SQL Server 2014  – here
SQL Server 2016 – here

New in 7.0.4.0

SQL Server 2008/2012/2014/2016

  • Updated the “Security Considerations” section in the
    operations guide
  • Updated the default value of SP Level in the “Service
    Pack Compliance” monitor for SQL Server 2012 (SP 4)
  • Added the actual value of free space (% and MB) in
    the alert description of the “Transaction Log Free
    Space (%)” monitor (SQL 2012 only)

SQL Server Dashboards

No changes introduced; increased the version number to 7.0.4.0 to
comply with the current version of SQL Server management packs

SCOM 2016: Updated SQL Management Packs v7.0.2.0

New versions of the SQL management packs have been released get them using the links below:

SQL Server 2016here
SQL Server 2014here
SQL Server 2008/2012here
SQL Server Dashboardshere

New in Version 7.0.2.0

SQL Server 2008/2012/2014/2016

  • Fixed issue: Always On data source scripts fail as Microsoft.SqlServer.Management.PSSnapins.dll is not imported
  • Fixed issue: Always On monitoring scripts may fail because of “No coercion operator is defined…” error (caused by an issue in PowerShell 5.0)
  • Fixed Dashboards issue: “DW data early aggregation” rule crashes on SCOM 2016

SQL Server Dashboards

  • Fixed issue: “DW data early aggregation” rule crashes on SCOM 2016

SCOM 2016: Updated MPs for SQL Server v7.0.0.0

The new management packs for SQL Server have been released get them at the links below:

SQL Server 2016

SQL Server 2014

SQL Server (2008-2012)

SQL Server Dashboards

 

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

SCOM 2016: Updated MP for SQL 2017+

Hot off the press an updated management pack for monitoring of SQL 2017 and all future versions of SQL get version 6.7.65.0 here

New in this version:

  • The management pack was reimplemented in order to enable monitoring SQL Server 2017 and all upcoming SQL Server versions
  • Introduced a number of fixes and improvements to functionality, performance, and display strings
  • Reduced the number of files in the management pack
  • Removed dependency on SQL Server Dashboards management pack