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.3
- In the CM Console, Data is not captured under the 'Target_Object' column for CREATE and DROP table commands, when 'SQL_Audit_Specification' event is used.
- Unknown publisher is displayed in UAC window during uninstallation.
- The "SQLCompliance Agent" program name is not displayed in the "UAC" message after starting the uninstallation from "Programs and Features".
- The old dashboard version does not update to the latest version 4.8.2
...
- after upgrading the CM build.
Known issues in version 6.2
- "Agent Trace " files are not being compressed when selected in Agent properties.
- Audit reports page is not displaying the UI options on the SQL CM web console when using Safari browser.
- Before After Data (BAD) with a server-level privileged user with enabled capture SQL statements are not capturing SQL statements.
- DB-level privileged users do not capture DML events for sensitive columns when the same column is added under BAD.
...
- 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.
- (Fixed in version 6.1) 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.
...