IDERA SQL Compliance Manager provides the following new features and fixed issues.
IDERA, Inc. customers are solely responsible for ensuring compliance with the laws and standards affecting their business. IDERA, Inc. does not represent that its products or services ensure that customer is in compliance with any law. It is the responsibility of the customer to obtain legal, accounting, or audit counsel as to the necessary business practices and actions to comply with such laws. |
8.2 Fixed Issues
Query & Permission Handling Improvements
SQL Compliance Manager 8.2 includes various bug fixes focused on improving query performance, ensuring better visibility in reports, and properly enforcing role and permission behavior.
Resolved an issue where the SELECT query execution took longer when DML auditing was enabled on the server.
SQL Compliance Manager 8.2 fixed an issue where the SELECT Statements captured variables instead of the actual value.
Fixed a case where the Login Parameter in the Reports section did not display the full list of logins, preventing reports from being run with all available options.
SQL Compliance Manager 8.2 fixed an issue where newly added console users were automatically granted the 'sqlcmuser' role (full permissions), even when only read-only access was intended. Users now receive only the roles explicitly assigned to them.
Fixed a case where Audit Events were not visible in the SQL Compliance console for users who were part of a Windows group, even when they had the necessary permissions.
Error Handling and UI Enhancements
SQL Compliance Manager 8.2 includes various enhancements in error handling and system messages to provide clearer guidance and a better understanding of actions and requirements
Fixed a case that allowed users to attempt creating additional Collection Services on a machine that only had the management console installed. The message has been updated to clearly state that multiple collection servers require the SQL CM services to be installed on the machine.
Addressed an issue where a misleading error message was displayed during a console-only installation process.
Improved and clarified the wording on the SQL Compliance pane used to enter credentials when adding an Azure Blob Storage.
SQL Compliance Manager 8.2 resolved an issue where the console attempted to start the Collection Service on the repository machine when the repository was on a separate machine from the services.
Fixed a case where a misleading error was shown when attempting to register a reachable instance while the Collection Service was not running.
Fixed a bug where SQL Server 2022 (Major Engine version 16.00) was not displayed in SQL Compliance Manager. SQL Compliance Manager 8.2 now supports and collects audit events from RDS servers running SQL Server 2022 (Major Engine version 16.00).
For more information about new features and fixed issues in version 8.1, see Previous new features and fixed issues.
