Page History

This build of IDERA SQL Compliance Manager includes many fixed issues, including the following updates.

5.4.2 New features

Supports TLS 1.2 with SQL CM 5.4.2

IDERA SQL Compliance Manager 5.4.2 includes support for Transport Layer Security (TLS) version 1.2. The TLS protocol provides encryption, authentication, and data privacy and integrity when transferring information over a network, including VPN, VOIP, and instant messaging.

5.4.2 Fixed issues

Administration issues

• Anchor
  SQLCM-4195 SQLCM-4195

  Resolved an issue causing both Primary and Secondary nodes to list the AlwaysOn database as Secondary.

• Anchor
  SQLCM-4924 SQLCM-4924

  Resolved an issue preventing email from working for certain servers and types of events.

Auditing issues

• Anchor
  SQLCM-2136 SQLCM-2136

  Resolved an issue preventing audit of the Availabiity Group listener if a non-default port is used.

• Anchor
  SQLCM-2216 SQLCM-2216

  Database-level Privileged User Auditing settings are no longer overwritten by instance-level Privileged User Auditing settings.

• Anchor
  SQLCM-3775, SQLCM-3648, SQLCM-4879 SQLCM-3775, SQLCM-3648, SQLCM-4879

  Resolved the following integrity check issues:
  • users received an integrity check issue message although the scheduled integrity checks all passed
  • SQL Server startup events caused an integrity check failure
  • Integrity checks didn't match the Audit events in the SQLCM Repository

• Anchor
  SQLCM-3789 SQLCM-3789

  Resolved an issue causing the database name to return blank for Login Events in some places.

• Anchor
  SQLCM-2529, SQLCM-4937 SQLCM-2529, SQLCM-4937

  SELECT statements no longer appear as UPDATE statements.

• Anchor
  SQLCM-3642 SQLCM-3642

  Resolved an error that occurred when the eventId reached the max limit of Integer. The error was, "Cannot insert duplicate key row in object 'dbo.Events' with unique index 'IX_Events_eventId'.

• Anchor
  SQLCM-4346, SQLCM-4621 SQLCM-4346, SQLCM-4621

  No longer generates the Column Value Changed Data alert twice for Before-After auditing events.

• Anchor
  SQLCM-4649 SQLCM-4649

  Resolved an issue causing an error when updating a table that contains an image and the table name contains a hyphen.

• Anchor
  SQLCM-4955 SQLCM-4955

  The default Events view now displays data for a single day rather than 30 days.

• Anchor
  SQLCM-4950 SQLCM-4950

  Resolved an issue preventing the proper function of the Exporting/Importing Database DML Filter audit settings.

Archiving issues

• Anchor
  SQLCM-2512, SQLCM-4919 SQLCM-2512, SQLCM-4919

  During archiving, users no longer receive a "Violation of PRIMARY KEY" error during archiving.

Reporting issues

• Anchor
  SQLCM-3788 SQLCM-3788

  Resolved an issue that prevented users from running the DML Activity (Before-After) report.

5.4.0 New features

...

• Anchor
  SQLCM-2163 SQLCM-2163

  Enabled Capture Transaction Status for DML Activity no longer replaces SQL statement values with variables.

• Anchor
  SQLCM-2171 SQLCM-2171

  This release resolves an issue that prevented auditing when two tables has the same name but different schema

• Anchor
  SQLCM-2174 SQLCM-2174

  An error no longer occurs while updating the audit configuration file due to duplicate database IDs.

• Anchor
  SQLCM-2175 SQLCM-2175

  Improves Collection Server performance while processing trace files.

• Anchor
  SQLCM-2351 SQLCM-2351

  Corrects an issue preventing the Collection Trace directory from being created when the user chooses a non-default installation path.

• Anchor
  SQLCM-3211 SQLCM-3211

  IDERA SQL Compliance Manager 5.3 now supports SQLcomplianceAgent SQL Compliance Manager Agent silent installation.

• Anchor
  SQLCM-3332 SQLCM-3332

  Resolves an issue causing heartbeat alerts for instances after they are archived.

• Anchor
  SQLCM-3637 SQLCM-3637

  Resolves an error that appeared when a user added privileged users while applying a custom Audit Collection Level.

• Anchor
  SQLCM-3638 SQLCM-3638

  Fixed an error causing the collection of non-audited database data when Capture SQL statements for DML and SELECT activity is enabled.

• Anchor
  SQLCM-3639 SQLCM-3639

  Before-After data now works during an update when auditing selected columns.

• Anchor
  SQLCM-3640 SQLCM-3640

  Non-AlwaysOn Availability Group databases can no longer be added to an AG server for auditing.

• Anchor
  SQLCM-4496 SQLCM-4496

  Resolves an issue causing an invalid object name error with 'sys.dm_os_window_info' for SQL Server 2005 agents.

...

• Anchor
  US16650, SQLCM-540 US16650, SQLCM-540

  Renamed the SQL Compliance Processing database from SQLCompliance.Processing to SQLComplianceProcessing.

• Anchor
  DE43945, SQLCM-2333 DE43945, SQLCM-2333

  Corrected an issue preventing the ... button from properly working in the Add SQLcompliance SQL Compliance Manager Agent Service window on Windows 2012/2012 R2 installations.

...

• Active Trace is now properly cleared when necessary.
• A change to the SQL Compliance Manager login filter settings from minutes to seconds fixes an issue that allowed new user events such as failed login attempts to be missed in reports.
• Reports now are viewable in .CSV format.
• SQL Compliance Manager 5.0 includes an update that clarifies alert email triggers when users to have two alert rules for Sensitive Columns.
• SQL Compliance Manager no longer displays conflicting data by including a fix that forces the collection of object names while processing trace file records.
• Normal user accounts are no longer able to capture SQL text used in admin activities without enabling additional options.
• When you have multiple columns selected for a particular table in Before-After Data (BAD), SQL Compliance Manager no longer labels events that update other columns as BAD events.
• SQL Compliance Manager now includes descriptions for ALTER ANY SCHEMA and ALTER ANY USER in the tracejob.cs file.
• The permissions check process is updated in SQL Compliance Manager 5.0 to avoid any issues when performing a check.
• Event types 158 and 258 now include expanded details that display when these types of events occur.
• SQL Compliance Manager Integrity Check now properly tracks and reports on deleted rows.

...

...

...

...

...