IDERA SQL Compliance Manager provides the following new features and fixed issues.
IDERA, Inc. customers have the sole responsibility to ensure their 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.
5.8.1 New Features
There are no new features in this release.
5.8.1 Fixed Issues
- Resolved the issue where the audit configuration was not updated when new users were added to a Windows Domain group which were previously configured as Trusted Users.
- Resolved the issue where public roles were granted unnecessary permissions such as ALTER, EXECUTE, CONTROL, TAKE OWNERSHIP, and VIEW DEFINITION, on the audit stored procedures sp_SQLcompliance_Audit and sp_SQLCompliance_StartUp.
- Resolved the issue where the Collection Server installer raised an error message requesting the removal of the newly restored SQLcompliance and SQLcomplianceProcessing databases. Currently, the migration of the Collection Server preserves the repository databases and displays the events on the console as expected.
- Resolved the issue where users were unable to register instances that are unreachable or from an untrusted domain. Currently, users are able to register unreachable instances or instances from untrusted domains. Please note that while unreachable instances can be registered for auditing, it is required for the Agent service to be deployed manually on these server instances.
For more information about new features and fixed issues in versions 5.7.x, see Previous new features and fixed issues.