...
| Warning |
|---|
IDERA, Inc. customers have the sole responsibility to ensure their compliance with the laws and standards affecting their business. IDERA, Inc. does not represent that its products or services ensures that customer is in compliance with any law. It is the responsibility of the customer to obtain legal, accounting, or audit counsel as to the necessary business practices and actions to comply with such laws. |
5.4.2 New features
| Warning |
|---|
IDERA SQL Compliance Manager 5.4 and later depend on certain Microsoft components that did not ship with SQL Server versions prior to SQL Server 2012 SP1. If you are installing SQL Compliance Manager's Collection Service on a Repository running on SQL Server 2012 or below, you must install these components manually. For more information about this process, see Important installation steps for SQLCM 5.4.x. |
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.
| 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
- 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.- Resolved an error that occured when the eventId reached the max limit of Integer. The error was, "Cannot insert dupicate 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.- 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 Exposting/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
- Resolved an issue that prevented users from running the DML Activity (Before-After) report.
5.4 New features
| Warning |
|---|
IDERA SQL Compliance Manager 5.4 depends on certain Microsoft components that did not ship with SQL Server versions prior to SQL Server 2012 SP1. If you are installing SQL Compliance Manager's Collection Service on a Repository running on SQL Server 2012 or below, you must install these components manually. For more information about this process, see Important installation steps for SQLCM 5.4.x. |
...