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 8.4
- There are no known issues with this release.
Known issues in version 8.3
- There are no known issues with this release.
Known issues in version 8.2
- There are no known issues with this release.
Known issues in version 8.1
- There are no known issues with this release.
Known issues in version 8.0
- Events are not captured on the Compliance Manager console for Azure Managed instances [SQLCM-7108].
- DML and Extended Events fail to generate in audit events with Extended Events as collection method when Trusted and Privileged users are selected at server level. [SQLCM-7103].
- SQL Trace Error on Remote Instance and Event Viewer Error Observed in the Remote VM when 2 collection servers are configured for 2 instances. [SQLCM-7101].
- Transaction Status for DML activity events are not generated for Extended Events and SQL Audit Specifications. [SQLCM-7095].
Known issues in version 7.0
- Duplicated events are captured when performing operations like INSERT, UPDATE, and administrative action queries on Azure MI auditing.
- In the CM console, DML Events are captured but not with the ('+') extension symbol sign where Sensitive columns are configured at database level during Azure MI auditing.
- DDL event is not captured at the Server level when Azure MI auditing.
...
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
...
- (Fixed in version 5.9) For registered SQL Server 2019 instances, the General tab of the SQL Server Properties window displays the version as Unknown. This is only a visual issue and does not affect auditing or any other functionality.
- (Fixed in version 5.9) The Audit settings Export feature does not export previously configured Server level Trusted Users. To complete the migration, add the Trusted Users manually at the Server Level.
- (Fixed in version 5.9) When you configure Sensitive Column auditing without first selecting the DML or SELECT option on the Audited Activities tab, then the SQLcompliance Agent has problems creating the sp_SQLcompliance_AuditXE stored procedure, and auditing stops working.
Sensitive Column issues
- |(Fixed in version 5.9)Events for Sensitive Column audit data are not captured when auditing via Extended Events. When the option to capture SELECT and DML activities is configured at the server-level to capture events via the Extended Events auditing method, and the capture SELECT and DML option is not configured at the database level but is configured to track SELECT and DML for Sensitive Column auditing. In order to capture and process Sensitive Column events correctly, change the collection method from Extended Events auditing to SQL Server Trace Files auditing.
...
- ( Fixed in version 5.4.2 ) The DML Activity (Before-After) report, when deployed to SQL Server Reporting Services, does not run properly. You can view the report in the Console.
...