IDERA strives to ensure our products provide quality solutions for your SQL Server needs. The following known IDERA SQL Compliance Manager issues are described in this section. If you need further assistance with any issue, please contact
| Newtablink |
|---|
| alias | Support |
|---|
| url | https://www.idera.com/support/supportplans |
|---|
|
.
Known issues in version 6.1
- Using "Extended Events" for collecting Audit data, a specific condition on database ID in certain event types causes queries executed under the context of different databases to not be collected, leading to missed audit data.
Known issues in version 6.0
- Switching from Extended Events or SQL Server Traces to SQL Server Audit Specification does not stop the pre-running audit sessions and audit files. After changing the selection to SQL Server Audit Specification, fresh audit data is collected through the Audit log files.
- SQL Compliance Manager sometimes displays an error message when the Agent service hits the trace start timeout while trying to cycle one of the audit traces it's running. As soon as the audit trace has been successfully restarted, auditing continues as expected, and the audit events captured in the trace will be processed into the audit trail in Compliance Manager without issues.
| Note |
|---|
|
This error does not affect auditing and can be safely ignored. |
For a particular Database configured to audit DML and SELECT activities via SQL Server Tracing, DML events when executed under a different Database context, produce T-SQL statements for the audited DML events showing variables over the actual values used in the transactions. DML events are captured as expected with actual parameters via SQL Server Tracing while using the same audited Database context.
- Entering passwords with special characters such as " / \ [ ] : ; | = , + * ? < > generates a failure with the installation, canceling and not completing the product installation.
...