IDERA SQL Inventory Manager 2.3 includes many fixed issues, including the following updates from previous releases.
2.2 New features
Supports core licensing for SQL Server 2012 and later
Users who have SQL Server 2012 and later instances using core licensing now can take advantage of the following additional core license-specific features and support available in IDERA SQL Inventory Manager 2.2:
- Supporting tables that help you identify core factors
- Additional core-specific information displayed in the SQL Server Licensing view
- Ability to edit Microsoft SQL Server license details
For more information about using SQL Server core licensing within IDERA SQL Inventory Manager, see How to manage SQL Server licensing.
Supports MS SQL Server 2016
IDERA SQL Inventory Manager 2.2 and later support hosting repositories and monitoring instances using SQL Server 2016. For more information about supported platforms, see Software requirements.
Improved performance
IDERA SQL Inventory Manager 2.2 includes a number of internal updates aimed at improving performance.
Allows configuration for some health checks
Users now can configure the alert threshold settings for the following health checks to customize alerts for particular environments:
- Database backup is not current
- SQL Server is down
- SQL Server is slow
For more information about customizing these health check alerts, see How to manage health checks.
2.2 Fixed issues
The following issues are fixed in IDERA SQL Inventory Manager 2.2 and no longer represent an issue:
Platform-specific fixed issues
- IDERA SQL Inventory Manager now successfully connects to SQL Server 2012 servers that have SP2 CU7 applied.
- IDERA SQL Inventory Manager no longer displays an incorrect version for SQL Server 2012 SP3. Previously, SQL Server 2012 SP3 appeared as SQL Server 2012 SP2.
Licensing fixed issues
- This release fixes an issue causing some users to experience the following error message when attempting to add a license key:
Missing resource message key= [com.idera.common.rest.RestException: An exception occurred setting the product configuration.] args=[]
Discovery fixed issues
- The Discovery Status log now correctly uses the localized data and time format. You can view a read-only log of all the actions and events occurring during the instance discovery process by clicking Discovery Status on the Administration tab.
Monitoring fixed issues
- Users now can successfully create an alias for an application that contains special characters in the current name.
- Users now can successfully use special characters in SQL Server instance locations.
- Improved metrics utilization in this release resolves an issue causing some users to see inconsistent server counts over a period of time