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

• Resolved an issue causing both Primary and Secondary nodes to list the AlwaysOn database as Secondary.
• Resolved an issue preventing email from working for certain servers and types of events.

Auditing issues

• Resolved an issue preventing audit of the Availabiity Group listener if a non-default port is used.
• Database-level Privileged User Auditing settings are no longer overwritten by instance-level Privileged User Auditing settings.
• 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
• Resolved an issue causing the database name to return blank for Login Events in some places.
• SELECT statements no longer appear as UPDATE statements.
• 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'.
• No longer generates the Column Value Changed Data alert twice for Before-After auditing events.
• Resolved an issue causing an error when updating a table that contains an image and the table name contains a hyphen.
• The default Events view now displays data for a single day rather than 30 days.
• Resolved an issue preventing the proper function of the Exporting/Importing Database DML Filter audit settings.

Archiving issues

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

Reporting issues

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

5.4.0 New features

Improves archiving through the availability of SQL Server Extended Events

IDERA SQL Compliance Manager 5.4 includes support for event handling with SQL Server Extended Events. This optional feature is available for use in auditing instead of using SQL Trace. Running Extended Events offers a performance improvement over the default SQL Trace audit event gathering system and is available for instances running SQL Server 2012 and later. For more information about using the Extended Events option, see Using SQL Server Extended Events.

Includes new Sensitive Column Search

Included in this release is integration with a free tool from IDERA called SQL Column Search. Available from the IDERA SQL Compliance Manager Instance Details view, this feature allows you to search tables and columns on a targeted database to discover the location of sensitive data needing to be audited. For more information about using the Sensitive Column Search, see Sensitive Column Search window.

Offers SQL Compliance Manager Windows Console functionality in the Web Console

The following features previously available only through the IDERA SQL Compliance Manager Windows Console now are available in the Web Console as well:

• Importing sensitive columns
• Importing audit settings including instance and database templates
• Exporting audit settings including instance and database templates

Includes updated regulatory guideline templates

IDERA SQL Compliance Manager includes a number of regulatory guideline templates for customer use. IDERA SQL Compliance Manager 5.4 includes updates for these templates. For more information about this feature, see Comply with specific regulations.

5.4.0 Fixed issues

Installation and upgrade issues

• Enabled Capture Transaction Status for DML Activity no longer replaces SQL statement values with variables.
• This release resolves an issue that prevented auditing when two tables has the same name but different schema
• An error no longer occurs while updating the audit configuration file due to duplicate database IDs.
• Improves Collection Server performance while processing trace files.
• Corrects an issue preventing the Collection Trace directory from being created when the user chooses a non-default installation path.
• IDERA SQL Compliance Manager 5.3 now supports SQL Compliance Manager Agent silent installation.
• Resolves an issue causing heartbeat alerts for instances after they are archived.
• Resolves an error that appeared when a user added privileged users while applying a custom Audit Collection Level.
• Fixed an error causing the collection of non-audited database data when Capture SQL statements for DML and SELECT activity is enabled.
• Before-After data now works during an update when auditing selected columns.
• Non-AlwaysOn Availability Group databases can no longer be added to an AG server for auditing.
• Resolves an issue causing an invalid object name error with 'sys.dm_os_window_info' for SQL Server 2005 agents.

5.3.1 New feature

Supports SQL Server 2016

IDERA SQL Compliance Manager 5.3.1 and later support audited and collection servers using Microsoft SQL Server 2016. For more information about supported platforms, see Software requirements.

5.3.1 Fixed issues

There are no fixed issues in this release.

5.3 New features

Expanded the SQL Compliance Manager Web console to provide a richer set of capabilities online

IDERA SQL Compliance Manager 5.3 continues to build on the work developed by prior versions to bring a richer set of capabilities to the web console. New web capabilities include:

• an ability to set up notifications for auditing thresholds; allowing a user to set up a threshold and select the delivery method such as email, Windows event log, or SNMP traps.
• additional views such as the Enhanced Audited Database, Enhanced Alert, and New Logs views.
• the ability to export views to PDF, CSV, and XML formats.
• additional new widgets that show different activities and audited SQL Server instances.

Integration with IDERA Dashboard 2.2

IDERA Dashboard integration began with SQL Compliance Manager 5.0, which centralizes the common administration, tasks, and views across all IDERA SQL products. This release of SQL Compliance Manager expands this integration by supporting IDERA Dashboard 2.2, which includes the following widgets specific to SQL Compliance Manager:

• SQL Compliance Manager Audited Instances Widget. Displays a list of audited SQL Server instances.
• SQL Compliance Manager Enterprise Activity Report Card. Displays your SQL Compliance Manager enterprise activity in a line graph.

For more information about using SQL Compliance Manager widgets within the IDERA Dashboard, see Use SQL Compliance Manager widgets in the IDERA Dashboard.

Limited Support for SQL Server 2016

IDERA supports installation of SQL Compliance Manager 5.3 on Microsoft SQL Server 2016 with limited technical support. Full technical support is available a short period after SQL Server 2016 is generally available.

5.3 Fixed issues

General

• Resolved an issue that did not properly update group permissions after modification and honored group settings over the individual user account in some situations.
• Improved Permissions Check functionality to prevent false or inconsistent results.

Installation

• Renamed the SQL Compliance Processing database from SQLCompliance.Processing to SQLComplianceProcessing.
• Corrected an issue preventing the ... button from properly working in the Add SQL Compliance Manager Agent Service window on Windows 2012/2012 R2 installations.

Licensing

• Resolved an issue causing users with AlwaysOn Availability Groups to receive a message that the maximum number of servers is reached while they actually had less than that limit.

Services

• Improved the Collection Service performance to be able to process a substantially large number of trace files.

Auditing

• SQL Compliance Manager now can log events that are accessed through a view.
• Sensitive column traces no longer include events from databases not configured for sensitive column auditing.
• Resolved an issue that prevented SQL Compliance Manager from discovering and auditing new users added to the list of Trusted Users / Privileged Users within a domain group without manually updating the audit settings.
• Exported audit settings now include database level privileged users.

5.0 New features

Fully supports the SQL Server AlwaysOn Availability Groups feature

SQL Compliance Manager 5.0 now allows DBAs to monitor their availability groups, availability replicas, and availability databases through AlwaysOn Availability in SQL Server 2012 and newer. AlwaysOn automatically switches auditing from the primary to the secondary replica in the event of failure as well as failback to primary when it comes back online. This advantage prevents a loss of audit data trail in the event of failure.

Support for this feature also comes with:

• An Availability Group Statistics report that allows you view the historical health of your availability groups, availability replicas, and availability databases.
• An Availability Group Topology report that allows you to view the current topology of your availability groups configuration.
• Monitoring of key metrics specific to the AlwaysOn Availability Groups feature.
• Queue Size and Transfer Rates charts.

For additional information on SQL Compliance Manager and the AlwaysOn Availability Groups feature, see Enable automatic failover using AlwaysOn Availability Groups.

Offers a technology preview of a new web-based SQL Compliance Manager Dashboard

Along with the integration of the IDERA Dashboard, SQL Compliance Manager 5.0 includes a preview of a newly-designed web console that offers quick views of key audit trail activities on your SQL Servers from any web browser. Identify key compliance issues quickly and provide an easy access point to non-DBAs without giving them access to the entire Management Console.

Added integration with the IDERA Dashboard

SQL Compliance Manager 5.0 now integrates with the IDERA Dashboard, a common technology framework designed to support the IDERA product suite. Users are able to obtain an overview of the status of their SQL Servers and hosted databases all in a consolidated view and navigate to individual product dashboards for details. The IDERA Dashboard provides a central set of services for managing users, product registry, instance registry, aggregated alerts across IDERA applications, a central web server, and tags for grouping instances. For more information about the IDERA Dashboard, see Navigate the IDERA Dashboard web console.

Moved to the Windows .NET 4.0 framework

SQL Compliance Manager 5.0 supports Microsoft Windows operating systems using .NET 4.0. Note that .NET 4.0 or later must be installed on the audited server. For more information about requirements, see Software requirements.

5.0 Fixed issues

• 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.