Versions Compared

Old Version 21

changes.mady.by.user Nicolas Rios

Saved on

compared with

New Version 22

changes.mady.by.user Nicolas Rios

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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


Expand
title5.5.1 New features

There are no new features in this release

Expand
title5.5.1 Fixed issues

Administration issues

  • Anchor
    SQLCM-4972
    SQLCM-4972
    IDERA SQL Compliance Manager 5.5.1 process version 4.5 traces files. After upgrading the Collection Server to version 5.5.1, the agent must be upgraded to the same version. Once both the Agent and the Collection Server upgrades are complete, SQL Compliance Manager will process trace files. For more information, see Upgrade to this build.

  • Anchor
    SQLCM-5339/5021/5243/5013/5340/5343
    SQLCM-5339/5021/5243/5013/5340/5343
    Resolved an issue in which the SQL Compliance Manager Collection Server was not processing trace files, or was processing them slowly, causing backlog files to get accumulated in the Collection Trace Directory in large transactional databases.

  • Anchor
    SQLCM-5306
    SQLCM-5306
    IDERA SQL Compliance Manager 5.5.1 installation no longer fails if TLS 1.0 is disabled and if SQL Server 2012 Native Client is not available.

  • Anchor
    SQLCM-5275/4919/2512
    SQLCM-5275/4919/2512
    IDERA SQL Compliance Manager 5.5.1 no longer shows the "Violation of PRIMARY KEY constraint" error nor terminates the statement when performing an archive of a highly transactional database. 

  • Anchor
    SQLCM-5264
    SQLCM-5264
    Integrity check runs for archived databases performed through stored procedures. 

  • Anchor
    SQLCM-5456
    SQLCM-5456
    IDERA SQL Compliance Manager 5.5.1 installation no longer fails due to an error setting up permissions if the username used special characters (e.g. ",", space characters, etc.).
  • Anchor
    SQLCM-4633
    SQLCM-4633
    IDERA SQL Compliance Manager 5.5.1 supports user names longer than 20 characters as well as special characters for the user's password, such as £.
Expand
title5.5.0 New features

Anchor
SQLCM-5042
SQLCM-5042
Includes updated and new regulation guidelines

IDERA SQL Compliance Manager 5.5 includes updates on PCI DSS and HIPAA regulation guidelines templates. It also includes new sets of regulation guidelines, allowing users to perform data audits according the corresponding security rules.

The new regulation guidelines are the following:

  • Defense Information Security Agency (DISA STIG)
  • North American Electric Reliability Corporation (NERC)
  • Center for Internet Security (CIS)
  • Sarbanes-Oxley Act (SOX)
  • Family Educational Rights and Privacy Act (FERPA)

For more information about this feature, see Comply with specific Regulations.

Auditing available via SQL Server Audit Logs

IDERA SQL Compliance Manager 5.5 includes the ability to track your alerts via SQL Server Audit Logs for Agents running on SQL Server 2017 or above. Users can now decide if they want to track events via Trace Files, Extended Events (SQL Server 2015 and above) or Audit Logs (SQL Server 2017 or above). This new feature is supported in both the Web console and the Windows Management Console.

For more information about this feature, see Using SQL Server Audit Logs.

Anchor
SQLCM-5044
SQLCM-5044
Includes a Row Count feature

IDERA SQL Compliance Manager 5.5 includes the row count feature which captures and reports on the frequency that users access Event types and SQL Statements, alerting database administrators about suspicious behavior.

Info

Anchor
SQLCM-5370
SQLCM-5370
As part of the row count functionality in SQL Compliance Manager 5.5 and above, we are now capturing Statement Completed instead of Statement Start.  In some cases, if a SQL statement is run but not executed (e.g. SET SHOWPLAN_XML), SQL Compliance Manager may pick up those events.

For more information about this feature, see Control data access - Row count.

Enable SQL Extended Events Auditing from the Windows Management Console

SQL Extended Events auditing can now be enabled from both the Web Console and the Windows Management Console.

For more information about this feature, see Using SQL Server Extended Events. 

Anchor
SQLCM-5043
SQLCM-5043
Supports SQL Server 2017

IDERA SQL Compliance Manager 5.5 now supports installation of the Database Repository for Collection Server, deployment of the SQL Compliance Manager Agent, and auditing events for SQL Server 2017.

For more information, see Software requirements. 

Anchor
SQLCM-5215
SQLCM-5215
Supports Windows Server 2016

The user can install IDERA SQL Compliance Manager 5.5 and deploy the SQL Compliance Manager Agent in Windows Server 2016. 

For more information, see Software requirements.  

Anchor
SQLCM-5044
SQLCM-5044
Allows users to create Sensitive Column data sets

IDERA SQL Compliance Manager 5.5 allows users to create Sensitive Column data sets that can be monitored as a group of sensitive information. Users can also add Sensitive Column data sets to any regulation guideline applied in servers or databases. 

For more information, see Sensitive Column window. 

Anchor
SQLCM-5105
SQLCM-5105
BAD Alerts

IDERA SQL Compliance Manager 5.5 allows users to add Host Name, Login, and Before-After data values to the alert message templates.

Agent Deployment method

IDERA SQL Compliance Manager 5.5 allows users to see the agent deployment method in the Registered SQL Servers window of the Administration view.

Anchor
SQLCM-4929
SQLCM-4929
Allows users to install or upgrade on a non default drive

IDERA SQL Compliance Manager 5.5 allows users to install and/or upgrade in a non default drive path. 

Expand
title5.5.0 Fixed issues

Administration issues

  • Anchor
    SQLCM-3759
    SQLCM-3759
    Audit thresholds appear enabled in the ReportCard even after removing and/or archiving an instance.     
  • Anchor
    SQLCM-4972
    SQLCM-4972
    SQL Compliance Manager 5.5 no longer fails to reach the Collection service on the active node after a successful failover in a clustered environment. 
  • Anchor
    SQLCM-5016/5017
    SQLCM-5016/5017
    Resolved the issue preventing SQL Scripts files with Supplementary Characters to work on the Collation SQL Server.  
  • Anchor
    SQLCM-3741
    SQLCM-3741
    Resolved the issue causing unexpected behavior during the manual upgrade of the SQL Compliance Manager Agent on a remote machine.
  • Anchor
    SQLCM-4674
    SQLCM-4674
    Resolved an issue causing overwritten permissions on the Agent Trace folder after deploying the SQL Compliance Manager Agent. 

Auditing issues

  • Anchor
    SQLCM-4952
    SQLCM-4952
    SQL Compliance Manager Agent no longer recreates stored procedures every second.
  • Anchor
    SQLCM-4947
    SQLCM-4947
    Resolved an issue in which SQL Compliance Manager was not showing Before-After data when enabling capture DML events using Extended Events. 
  • Anchor
    SQLCM-4574
    SQLCM-4574
    Resolved an issue causing DDL Events to display twice for the same event. 
  • Anchor
    SQLCM-4211
    SQLCM-4211
    Resolved an issue in which SQL Compliance Manager was not saving changes made in privileged users when applying regulation guidelines.
  • Anchor
    SQLCM-4680
    SQLCM-4680
    Resolved the issue preventing the user to capture SQL Statements for DDL and Security changes.
  • Anchor
    SQLCM-4947
    SQLCM-4947
    Resolved the issue preventing the capture of Before-After Data when using Extended Events auditing to capture DML events.

Reporting issues

  • Anchor
    SQLCM-4898
    SQLCM-4898
    Email notifications for Event Alerts now display the date and time in the Collection Server time zone. 

  • Anchor
    SQLCM-4645
    SQLCM-4645
    SQL Compliance Manager alerts users about the limit of SQL Statements when exporting reports. 

  • Anchor
    SQLCM-4850/4741
    SQLCM-4850/4741
    Resolved an issue preventing users to view and report on audit data or see events. 

...

Expand
title5.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-3775, SQLCM-3648, SQLCM-4879
    SQLCM-3775, SQLCM-3648, SQLCM-4879
  • 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.

...

Expand
title5.3.0 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 DashboardOverview tab.

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.

...