Page History

...

Auditing issues

• Anchor
  SQLCM-3827 SQLCM-3827

  Security changes are not captured when Capture SQL Statements for DLL is enabled.

• Anchor
  SQLCM-3739 SQLCM-3739

  While the IDERA SQL Compliance Manager Web Console Audit Event Filters view displays Enable or Disable in the Status column, the exported file displays only a 1 in that same column and for both statuses.

• Anchor
  SQLCM-3640, SQLCM-3639 SQLCM-3640, SQLCM-3639

  After registering an AlwaysOn Availability Group server for auditing using the Listener method, IDERA Compliance Manager:
  • allows auditing of all databases for the Primary node, including those that are not part of the AG. Note that if the primary node changes, the non-AG databases will not be available.
  • (Cluster Agent configured on nodes) returns an error after running the update query with one column of a table selected for Before and After auditing OR when you select Audit Selected Columns with all columns selected instead of checking Audit All Columns. While the data is updated in the table, no Before and After data is collected.

• Anchor
  SQLCM-3637 SQLCM-3637

  If you select Custom for the Audit Collection Level and attempt to add privileged users when adding a new database for auditing, an error occurs when you click Add. To avoid this issue, add the new database without selecting any privileged users, and then go back and edit the properties for the audited database and add a privileged user.

• Anchor
  SQLCM-2229 SQLCM-2229

  When adding or removing a database role for a user on SQL Server 2008 R2, the audited event does not capture the SQL statement.

• Anchor
  SQLCM-2171 SQLCM-2171

  If you have two tables in the same database that have the same name but different schemas, auditing fails on those two tables.

• Anchor
  SQLCM-2163 SQLCM-2163

  When Capture Transaction Status for DML Activity is enabled for auditing on the database, capturing SQL Statements will have variables instead of values.

• Anchor
  SQLCM-3648 SQLCM-3648

  Some SQL Server startup/stop events may cause the integrity check to fail.

• Anchor
  SQLCM-3647 SQLCM-3647

  Case-sensitive collation may prevent some trusted and privileged users from being captured.

...

Save

Save