Version 107 of the Microsoft: SQL Server Enhanced PowerPack includes updating the PowerPack to be compatible with Python 3 and updates to Dynamic Applications.
-
Minimum Required SL1 Version: 12.1.0
- Other Key Information:
- Additional permissions are required for the user account SL1 uses to perform collection. See the Required Permissions section of this document for more information. If you are currently monitoring devices using the PowerPack, you must update the permissions of the user account you are using to monitor those devices. New Dynamic Applications will be aligned to existing devices during the next discovery of those devices.
- This version of the PowerPack requires PowerShell version 3.0 or later to be installed on the monitored SQL Servers.
- The SQL Servers that you monitor must have the SQL Server PowerShell module installed.
Before You Install or Upgrade
Ensure that you are running version 12.1.0 or later of SL1 before installing "Microsoft: SQL Server Enhanced" PowerPack version 107.
For details on upgrading SL1, see the relevant SL1 Platform Release Notes.
In addition, ensure that the SQL Servers you want to monitor are running PowerShell 3.0 or later.
Required Permissions
Version 107 of the Microsoft: SQL Server Enhanced PowerPack requires the following permissions for the user account used for monitoring:
- SQL 2014 and later versions require one of the following configurations:
- The user account has an enabled login on every instance and database to be monitored, with CONNECT SQL, VIEW SERVER STATE, and CONNECT ANY DATABASE permission granted to the login on each instance. The login should have VIEW DATABASE STATE permission and DB_DATAREADER role granted on the 'master' database, and the DB_DATAREADER role granted on the 'msdb' database.
- The user account has an enabled login on every instance and has the SYSADMIN role.
- SQL 2012 requires one of the following configurations:
- The user account has an enabled login on every instance and database to be monitored, with CONNECT SQL and VIEW SERVER STATE granted to the login on each instance. The login should also have VIEW DATABASE STATE permission and the DB_DATAREADER role granted on the 'master' database, and the DB_DATAREADER role granted on the 'msdb' database. In addition, every database in the instance should have CONNECT access granted to the login.
- The user account has an enabled login on every instance and has the SYSADMIN role.
Installation and Upgrade Process
If you are currently using the Dynamic Applications in this PowerPack to monitor devices, collection errors might occur for one or two polling cycles during the installation of a new version. To prevent collection errors during an upgrade, you can optionally disable collection for monitored devices before performing the following steps and re-enable collection after the upgrade.
To install this PowerPack:
- Search for and download the PowerPack from the PowerPacks page (Product Downloads > PowerPacks & SyncPacks) at the ScienceLogic Support Site.
- In SL1, go to the PowerPacks page (System > Manage > PowerPacks).
- Click the Actions menu and choose Import PowerPack. The Import PowerPack modal appears.
- Click PowerPack file from step 1. and navigate to the
- Select the PowerPack file and click . The PowerPack Installer modal displays a list of the PowerPack contents.
- Click PowerPack is added to the PowerPack Manager page. . The
Features
This release includes the following features:
- Dynamic Applications to discover and monitor SQL servers and their component devices
- Event Policies that are triggered when SQL Server components meet certain status criteria
- Device Classes for each type of SQL Server components device monitored
- An example credential you can use to create PowerShell credentials to connect to SQL servers
Enhancements and Issues Addressed
The following enhancements and addressed issues are included this release of the "Microsoft: SQL Server Enhanced" PowerPack:
- Updated all Dynamic Applications in the PowerPack to be compatible with Python 3.
- Updated the "Microsoft: SQL Server Instance Discovery" Dynamic Application to no longer discover stopped instances of Microsoft SQL Server. (Support Case: 00306828)
- The following collection objects were added to the "Microsoft: SQL Server Instance Configuration" Dynamic Application to track Microsoft SQL Server nodes and provide an alert on failover to the current owner of the instance:
- Currently Active Node
- Node Name
- Node Status
- Node Status Description
- Owner Node
- Updated the snippet code in the following Bulk Snippet Dynamic Applications to include device ID information when an internal alert is generated:
- Microsoft: SQL Server Buffer Performance
- Microsoft: SQL Server Database Cache Performance
- Microsoft: SQL Server Database Configuration
- Microsoft: SQL Server Database Performance
- Microsoft: SQL Server File Groups Configuration
- Microsoft: SQL Server File Groups Performance
- Microsoft: SQL Server Instance Cache Performance
- Microsoft: SQL Server Instance Performance
- Microsoft: SQL Server Memory Performance
- Microsoft: SQL Server Performance
- Microsoft: SQL Server Remote Server Configuration
- Microsoft: SQL Server Session Performance
- Microsoft: SQL Server Table Lock/Latch Performance
- Addressed an issue in the PowerPack in which extended characters in a database name returned a hex-encoded string instead of the sanitized database name, and applied rounding to elapsed time collection objects in the "Microsoft: SQL Server Long Jobs Configuration" and "Microsoft: SQL Server Long Queries Configuration" Dynamic Applications.
Known Issues
The following known issues affect version 107 of the Microsoft: SQL Server Enhanced PowerPack:
- SQL Server instances with a "$" in the instance name will not discover databases or collect data. The instance name displayed in SL1 will contain only the characters after the "$".
- The "GetDB-Counters" snippet in the "Microsoft: SQL Server Database Performance" Dynamic Application will not collect data when the performance counter cannot be found. To address this, you will need to rebuild the performance counter manually. See the Microsoft documentation for the steps to rebuild the performance counter: https://docs.microsoft.com/en-us/troubleshoot/windows-server/performance/manually-rebuild-performance-counters
- The Microsoft: SQL Server Dashboard PowerPack is not compatible with the Microsoft: SQL Server Enhanced PowerPack.
- The performance Dynamic Applications in the PowerPack do not collect data for SQL Server x86 instances installed on a 64-bit platform.
-
Upgrading to from v103 to v104 may log an exception which includes
“get_cached_dictionary - Exception for 8C0F8D1AB88C18E1ADD9DFA4A0D43E50_SqlInventoryCache_52_Me_SqlDatabase.CLUS_INST02.model.52 - __new__() takes exactly 13 arguments (12 given)”
The exception does not recur on subsequent collections.