- 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.
|Anchor||SQLCM-6247/6223||SQLCM-6247/6223Resolved the issue where after a software upgrade, the console reports and/or the newly SSRS deployed reports fail to execute with the following syntax error: "Query execution failed for dataset 'ReportOutput'. (rsErrorExecutingCommand) Incorrect syntax near')'.|
For more information about new features and fixed issues in versions 5.7.x, see Previous new features and fixed issues.