SQL Inventory Manager v2.6.2
Released: Mar 1, 2021
v2.6.2 での更新項目
不具合の修正
- User Account Control window displays SQLInventoryManager properly when installing SIM 2.6.2.
- SIM 2.6.2 adds any unreachable instance correctly, and displays the proper informational message.
- User Account Control window displays IDERA as the SQL Inventory Manager publisher.
- SIM 2.6.2 registers successfully SQL Server instances, and cloud instances with SQL credentials only.
- SIM 2.6.2 gets registered successfully, and all the navigation screens work properly after being installed to CWF 4.6.0.40 with FIPS compliant for hashing, and signing, enabled.
- The Web Application logs do not show the password details in plain text anymore.
- SIM 2.6.2 discovers SQL Instances hosted in other domains properly.
- The SQL Server is Down alert is properly described in Manage Health Checks.
- In the Explorer view, the data now displays correctly, ordered by size, sorted in descending order, and with proper values till two decimal places.
- The Instance is Down email alerts work as expected after upgrading SIM.
- The Repository is installed/upgraded correctly, even when the database name is changed from the default settings.
- After entering the vCenter information in the Manage VM Configuration, the settings for VM configuration are saved and work properly.
- When reports to SSRS are deployed, these reports share data source configured with appropriate value and custom data source as empty.
- SIM 2.6.2 is successfully installed on Windows Server 2012 with SQL Server 2014 Standard.
- Databases on the secondary node of an Availability Group do not raise Databases Without a Backup health checks anymore.
- Dropped databases do not show up in the Databases list displayed under the Instance Details page.
- Custom field value from the Instance Summary view, now fully displays.
- The comments added to the Database Details screen for a monitored database are properly displayed when the p_InsertUpdateDatabase stored procedure runs as part of a data refresh.
- The Data Space at Risk alert works properly when Autogrowth is either disabled, enabled with limited file size, and enabled with unlimited file size.