Versions Compared

Old Version 1

changes.mady.by.user Nadja Pollard

Saved on

compared with

New Version Current

changes.mady.by.user Rodrigo Rivero

Saved on

Key

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

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

Expand

...

title6.

...

1 New features

...

  • Anchor
    SQLCM-6350
    SQLCM-6350
         SQL Compliance Manager

...

Supports Windows Server 2012 cluster deployment

This version of SQL Compliance Manager allows you to install in a Windows Server 2012 clustered environment. For more information about this feature, see Deploy SQL Compliance Manager in a Windows Server 2012 clustered environment.

Audit the local SQL Server instance running the Collection Server on a cluster

SQL Compliance Manager allows you to audit a virtual SQL Server instance including the local instance on a cluster running the Collection Server. For more information about auditing a virtual SQL Server instance, see Audit a virtual SQL Server instance.

Schedule automatic archives

SQL Compliance Manager now allows you to schedule automatic archiving. You can select from daily, weekly, or monthly options. This feature is disabled by default. You can enable this feature and manage these settings in the Archive Preferences window.

Specify archive database drive

When setting up archiving, you can specify the drive where you want SQL Compliance Manager to store the archive database. You can manage this location in the Archive Preferences window.

Receive alerts through SNMP

Users now can select to receive alerts as SNMP Trap messages to a specified destination network management console. For more information about creating a new event rule to includes SNMP Traps, see New Event Alert Rule wizard - Alert Actions tab.

Before-After data values display NULL when there is no value

After collecting data, if there is no before or after data available, SQL Compliance Manager displays "NULL" in the Before Value and After Value columns of the Event Properties window. For more information about Before-After data, see Audited Database Properties window - Before-After Data tab.

Supports PCI DSS v3

SQL Compliance Manager now supports Payment Card Industry Data Security Standard (PCI DSS) v3.0.

Improved table compression

The data type is changed in a number of highly-utilized tables from NTEXT to VARCHAR in an attempt to improve data compression.

Improved installation process

The SQL Compliance Manager installer now checks the permissions on the trace directory and the IDERA folders to ensure that the service account is appropriately added with full control permissions for processing.

Improved database usage regarding failed inserts

SQL Compliance Manager includes new code that allows it to reuse event IDs in the event of a failed data insert.

4.5 Fixed issues

  • SQL Compliance Manager includes new code regarding the threading library, making sure that all files in the trace directory are successfully processed. This fixes an issue that caused large trace file backlogs in the Collection Server.
  • The Administrative Activities Audit Option no longer re-enables automatically after disabled.
  • Users no longer receive an error when processing the trace file due to a limited column size in the table associated with Before-After Data.
  • Users upgrading from SQL Compliance Manager 3.7 to 4.3 no longer receive numerous file parsing errors.
  • This release fixes an issue causing incorrect dates to appear if you have SELECT and Sensitive Columns enabled in the Audited Database Properties window. Previously, if the Database SELECT operations check box on the Audited Activities tab, and the Sensitive Columns tab includes All Columns of the dbo.Customers table, the dates in the summary for the associated SQL Server instance were incorrect.
  • An issue that prevented new SQL Compliance Manager Agent files from processing after adding a second node to a clustered repository no longer occurs.
  • All failed integrity checks now includes specific events in the Details area of the Integrity Check Results window.
  • Users no longer experience missing registry keys after re-adding monitored SQL Server instances.
  • Adding an audited database to a monitored SQL Server instance no longer returns the server settings to default.
  • Providing read-only access to the SQLcompliance database no longer requires that the GUEST account be enabled.

4.3 New features

SQL Compliance Manager 4.3 now offers a Collection Server-only install

SQL Compliance Manager 4.3 now allows you to install the Collection Server and Repository only to support installing SQL Compliance Manager on a cluster.

4.3 Fixed issues

There are no fixed issues in this release.

4.2 New features

New Family Educational Rights and Privacy Act (FERPA) guideline

Apply the new FERPA regulatory guideline to ensure your audited databases meet the requirements of this legislation. You can apply this guideline through the CLI or through the Import Audit Settings feature in the Console.

FERPA was introduced in 1974. This federal law mandates the confidentiality and protection of student information in any educational institution that receives funding from the Federal Government from kindergarten through the university level. FERPA generally prevents an education agency or institution from sharing student records or personally identifiable information in those records with individuals who are not authorized to view that information. In some cases authorized individuals need to be monitored to deter insider theft and unauthorized dissemination of information.

New Sarbanes Oxley (SOX) guideline

Apply the new SOX regulatory guideline to immediately enforce the right auditing settings for sensitive financial data. Collect a detailed audit trail of all access to that data and then deliver reports that prove your compliance to auditors. You can apply this guideline through the CLI or through the Import Audit Settings feature in the Console.

SOX, also known as the Corporate and Auditing Accountability and Responsibility Act, was first introduced in 2002. This legislation was put in place as a response to the corporate and accounting scandals which cost investors billions of dollars. From an information technology standpoint, security professionals and database administrators must collectively implement policies and processes that audit permissions on, and access to, financial data as well data changes such as before and after values.

New CLI actions register instances and apply audit settings

Use the new command line interface (CLI) actions to quickly and easily register large numbers of SQL Server instances and immediately apply audit settings to the hosted databases. You can choose to apply the default audit settings, custom audit settings you have exported from another audited instance, or a regulation guideline.

4.2 Fixed issues

  • When the T-SQL query associated with an event cannot be parsed, SQL Compliance Manager now captures the SQL statement and indicates that it could not be parsed. This issue was mostly likely to occur when auditing sensitive column access.
  • The Details tab of the Event Properties window now displays the SQL statement that is issued to SQL Server before SQL Server performs its query parameterization. This code represents the initial T-SQL query executed by the user.

4.0 New features

Offers HIPAA compliance guideline support

Collect data that helps you align with nine Health Insurance Portability Accountability Act (HIPAA) citations and one HITECH requirement via an out-of-the-box, customizable template.

Includes PCI compliance templates

Use the new, customizable auditing templates to help you comply with eight Payment Card Industry Data Security Standards (PCI DSS) requirement guidelines.

Provides Regulation Guideline reporting

The Regulation Guidelines report includes details for all of the guidelines applied to the databases on the selected SQL Server instance.

Features a new SQL Compliance Manager Configuration Wizard for ease of use

The new SQL Compliance Manager Configuration Wizard allows you to use a single wizard to register SQL Server instances, deploy the SQLcompliance Agent, add databases for audit, configure your audit settings for selected regulatory guidelines, and more.

4.0 Fixed issues

  • SQL Compliance Manager now properly processes Grant statements.
  • An issue causing SQL Compliance Manager to record Create and Drop Index events as Alter User Table events no longer occurs.
  • SQL Compliance Manager now loads custom reports on the Archived Events page without requiring the user to select a filter.
  • SQL Compliance Manager now honors the DML/SELECT filters if you enable both Select auditing and Sensitive Column Auditing.
  • SQL Compliance Manager now properly applies event filters for instances using non-standard ports.

3.7 New features

SQL Server 2012 compatible with experimental support

SQL Compliance Manager 3.7 is SQL Server 2012 RTM compatible. This version of SQL Compliance Manager is not certified against newer builds of SQL Server and should not be used with these builds in a production environment. IDERA provides experimental support while you use your installation in a testing environment to ensure the features you rely on most are working as, or better than, expected.

3.7 Fixed issues

There are no fixed issues in this release.

3.6 New features

New sensitive column alerting

You can now receive alert notifications when someone accesses a sensitive column in your audited databases.

Improved integrity check user interface

The Integrity Check Results window now indicates when before-after data associated with DML events and sensitive column access data associated with SELECT events have been modified or deleted.

3.6 Fixed issues

The following reports now include the option to view related data from all audited SQL Server instances in your environment:

  • Database Schema Change History
  • Object Activity
  • User Login History

3.5 New features

Sensitive column auditing

Track who has "selected" data from any number of columns in your audited tables and proactively identify malicious intent.

Transaction status auditing

Audit the status of any transaction that executes DML activity on your audited database. This audit data enhancement includes rollbacks and save points, allowing you to recognize suspicious activity.

3.5 Fixed issues

The Management Console now correctly imports alert rules exported from version 3.3 or earlier.

3.3 Fixed issues

  • SQL Compliance Manager now supports auditing SQL Server instances located in environments that require FIPS compliance.
  • The Collection Server now no longer performs duplicate processing of events collected in high-traffic environments. When this issue occurred, SQL Compliance Manager would write error and warning messages to the application event log, stating that it was either unable to read a trace file due to insufficient privileges or unable to delete the trace file due to a SQL Server lock.
  • You can now successfully audit before-after data for DML events that occur on SQL Server databases hosted by a Windows Server Cluster.
  • The DML/SELECT Filters tab of the Audited Database Properties window now allows you to successfully enable before-after auditing for DML events on specific database tables.

3.2 Hotfix 1 Fixed issues

  • The SQLcompliance Agent now correctly handles a fail over that occurs on an active-active Windows cluster.
  • When storing DML events collected for Before-After auditing, event processing now correctly stores each event only one time for statements that insert more than 1000 rows.

3.2 Fixed issues

  • The SQLcompliance Agent now refreshes its list of DBID (database identifier) properties at each heartbeat. This fix ensures that SQL Compliance Manager can continue collecting audit data for a database after its ID number changes. For example, database ID numbers can change when a database is dropped, backed up, re-attached, or restored.
  • The groom job now correctly deletes all events older than the specified age.
  • The groom job now correctly identifies the SQL Server version, ensuring it grooms before and after data generated by DML events in SQL Server 2005 or later only. The ability to collect before and after data is not supported on SQL Server 2000 instances. 
  • Event Filters now support blank, empty, or null values when specifying application and host names.

3.1 Hotfix 1 Fixed issues

  • When attempting to audit DML activity on specific databases, the SQLcompliance Agent would sometimes fail to collect the DML events according to your audit settings. With this hotfix, the SQLcompliance Agent correctly audits the specified databases for DML activity.
  • After enabling the ability to audit Before-After data on database tables, SQL Compliance Manager would require accounts to have administrator privileges to the tables created by SQL Compliance Manager in order to modify data in the audited table, potentially preventing third-party applications and other accounts from writing to these tables. This hotfix allows SQL Server logins to read and write to the audited tables per the assigned privileges.
  • When attempting to groom audit data from a SQL Compliance Manager Repository hosted on a SQL Server 2000 instance, the grooming process would fail, returning the error “incorrect syntax near the keyword 'TOP'”. With this hotfix, you can successfully groom the Repository.
  • When you attempt to update the archive database indexes using the command-line interface or the Management Console, the update process would fail. With this hotfix, you can successfully update all archive databases to the new Repository schema.
  • The Management Console did not correctly format statistics with large values, resulting in an incorrect Processed Events statistic on the Explore Activity views. This hotfix resolves these formatting issues.

 

SQL Compliance Manager audits all activity on your server. Learn more > >
  • 6.1 adds a new feature “Auditing the IP address of the source of an event” which allows SQL Compliance Manager to capture and record the IP address of the source of an event along with other relevant information. It is configurable in the Audited Activities tab.
  • Anchor
    SQLCM-6458
    SQLCM-6458
    SQL Compliance Manager 6.1 improved to detect all the manual changes made to the [Events] and [EventSQL] tables by an Integrity Check.
  • Anchor
    SQLCM-6608
    SQLCM-6608
    SQL Compliance Manager 6.1 adds support for Windows 11 and Windows Server 2022 for installation and features. For more information on the operating system support, visit the Software Requirements page.
Expand
title6.1 Fixed issues
  • Anchor
    SQLCM-6435
    SQLCM-6435
         When running reports in both the Windows Console and Reportings Services you can now select multiple instances in the <Server Instance> dropdown.
  • Anchor
    SQLCM-6495
    SQLCM-6495
         Report Results rows now can be configured to use more than 10K Event Records.
  • Anchor
    SQLCM-6486
    SQLCM-6486
         Added a Horizontal Line in the Reports allowing users to adjust the space that the filters or the report use at any given time. Also added a horizontal scrollbar allowing the user to navigate through the reports.
  • Anchor
    SQLCM-6438
    SQLCM-6438
         Resolved the issue where running the SQL Server Reporting Services listed all users in a long string in the report output when all users are selected.
  • Anchor
    SQLCM-6368
    SQLCM-6368
         Fixed an issue where an error occurred during the setup of the Collection Service account with a password longer than 32 characters during the installation.
  • Anchor
    SQLCM-6506
    SQLCM-6506
         Resolved the issue where auditing via extended events and making changes to the temp-tables caused to "Audit all user tables" when "DML\SELECT Filters" was configured.
  • Anchor
    SQLCM-6377
    SQLCM-6377
         Resolved an issue where the DataChanges table showed a number of eventId     ` s with a value of NULL.
  • Anchor
    SQLCM-6482
    SQLCM-6482
         Fixed an issue where the error prompted "An item with the same key has already been added" prompted while loading configuration for the SERVER and occurred when having two databases with the same id but different names.
  • Anchor
    SQLCM-6526
    SQLCM-6526
         Resolved the issue where SSMS native activities were picked up when using Extended Events as the collection method.
  • Anchor
    SQLCM-6440
    SQLCM-6440
         Resolved the issue where an error appeared when opening Excel export of "Regulatory Compliance Check" report in SSRS.
  • Anchor
    SQLCM-6441
    SQLCM-6441
         Fixed the issue where the Audit Events View didn't keep custom columns after the console was restarted.
  • Anchor
    SQLCM-6458
    SQLCM-6458
         Fixed an issue where making changes to the [EventSQL] table was not picked up by the Integrity Check.
  • Anchor
    SQLCM-6591
    SQLCM-6591
         Resolved an issue where the Login Filter was recording the same login multiple times.
  • Anchor
    SQLCM-6359
    SQLCM-6359
         Excel report export no longer rounds up event timestamps.
  • Anchor
    SQLCM-6267
    SQLCM-6267
         Resolved an issue where Trusted User registration was case-sensitive for an auto-registered new database while it was case-insensitive for manually registered databases.     
Expand
title6.0 New features
  • Anchor
    SQLCM-6350
    SQLCM-6350
         SQL Compliance Manager 6.0 extends the capabilities of the current SQL CM Agent to support remote auditing on SQL servers on EC2. Allowing users to add SQL Servers active on the share network location to write/read data and support DBaaS SQL Server Instances.  The Cloud Agent consists of the same behavior and functionality as the current SQL Agent, but the RDS agent is a separate agent deployed into the cloud with its own configuration auditing settings.
  • Anchor
    SQLCM-6489
    SQLCM-6489
    SQL Compliance Manager 6.0 adds support for Amazon RDS to audit servers, databases, Sensitive Data, and Activities while alerting and reporting on them. Users can select Amazon RDS as their Server Type when adding a new server in the Specify SQL Server configuration window. According to the selection, SQL CM asks to Specify Connection Credentials for the authentication, and once registered, users can begin auditing the database activity on that server.
  • Anchor
    SQLCM-6557
    SQLCM-6557
    SQL Compliance Manager 6.0 permits the creation of storage accounts to place its components within AWS. In Amazon RDS, users can audit Microsoft SQL Server databases using the built-in SQL Server auditing mechanism. For additional information on Support for SQL Server Audit, visit the SQL Server Audit User Guide.
  • Anchor
    SQLCM-6555
    SQLCM-6555
    Upon upgrading to SQL CM 6.0 or preparing a new installation, SQL Compliance Manager Event Collection Method Capture Default Setting changes to "SQL Server Audit Specifications". All audit logs for 'DML and Select Activities' are captured and filtered properly both for the existing CM architecture and the cloud support platform. 
Expand
title6.0 Fixed issues
  • Anchor
    SQLCM-6555
    SQLCM-6555
         Resolved the issue where users were mistakenly prompted for an agent upgrade. Now, if the Agent is on the latest version, the Upgrade Agent displays as a non-clickable out.
Expand
title5.9 New features

There are no new features in this release.

Expand
title5.9 Fixed issues
  • Anchor
    SQLCM-6385
    SQLCM-6385
         Exporting Audit Settings now successfully includes an export of the Server Level Trusted Users configured . 
  • Anchor
    SQLCM-6259
    SQLCM-6259
         Resolved the issue where the SQL Server Properties window displayed the version as Unknown for registered SQL Server 2019 instances. Now, the correct version is shown. 
  • Anchor
    SQLCM-6407
    SQLCM-6407
         Resolved the issue where auditing stopped working when a user-configured Sensitive Column auditing without first selecting the DML or SELECT option caused the SQLcompliance Agent to have problems creating the sp_SQLcompliance_AuditXE  stored procedure.
  • Anchor
    SQLCM-6277
    SQLCM-6277
         Resolved the issue where Events were not captured for sensitive columns when SELECT and DML are not enabled at database-level audited activities on fresh and upgraded setups.
  • Anchor
    SQLCM-6463
    SQLCM-6463
         The DML Activity (Before-After) report shows accurate results regardless of the collection method being set to Extended Events or SQL Tracing.
  • Anchor
    SQLCM-6460
    SQLCM-6460
         The DML\SELECT filters are now working correctly when auditing SQL Server 2019 and no longer prevent DML and SELECT activities from being audited accordingly.
  • Anchor
    SQLCM-6457
    SQLCM-6457
         The following error is no longer observed when attempting to run DML changes on a table configured for Before-After auditing in the software.     "The DELETE permission was denied on the object 'SQLcompliance_Changed_Data_Table'."
  • Anchor
    SQLCM-6379
    SQLCM-6379
         The retention period of the Activity Log is now configurable. It is set to a default of 60 days which can be modified in the SQLcomplianceCollectionService.exe.config file in the MAX_ACTIVITY_LOGS_AGE flag.
  • Anchor
    SQLCM-6376/6365
    SQLCM-6376/6365
         Console loading times are faster now at both console startup and when navigating to the Audit Events view of the audited server or database.
  • Anchor
    SQLCM-6370
    SQLCM-6370
         Event details on INSERT and DELETE events, audited not as INSERT INTO or DELETE FROM executions, are no longer missing the Target Object Name information, showing the name of the database object affected by the audited DML change.
  • Anchor
    SQLCM-6349
    SQLCM-6349
         Reports deployed to SQL Server Reporting Services now show corresponding logins in the Login dropdown filter when these are set to run against an archived database.
  • Anchor
    SQLCM-6223
    SQLCM-6223
    Reports no longer show a syntax error when executed either from the console application or SQL Server Reporting Services.
  • Anchor
    SQLCM-6149
    SQLCM-6149
    The permissions check for the SQL Server service account permissions on the Agent Trace Files folder no longer fails when the SQL Server is running under the NETWORK SERVICE service account.
  • Anchor
    SQLCM-6327/6193
    SQLCM-6327/6193
         Data types have been updated in the tables saving Before-After data to prevent the tables from filling up with event data too soon. This would have prevented new events from processing otherwise, as a result.
  • Anchor
    SQLCM-6367
    SQLCM-6367
         The console application logging is no longer showing a collation conflict error, as shown below:      "Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation."
Expand
title5.8.1 New features

There are no new features in this release.

Expand
title5.8.1 Fixed issues
  • Anchor
    SQLCM-6134
    SQLCM-6134
    Resolved the issue where the audit configuration was not updated when new users were added to a Windows Domain group which were previously configured as Trusted Users. 
  • Anchor
    SQLCM-6219
    SQLCM-6219
    Resolved the issue where public roles were granted unnecessary permissions, such as ALTER, EXECUTE, CONTROL, TAKE OWNERSHIP, and VIEW DEFINITION, on the audit stored procedures sp_SQLcompliance_Audit and sp_SQLCompliance_StartUp .
  • Anchor
    SQLCM-6230
    SQLCM-6230
    Resolved the issue where the Collection Server installer raised an error message requesting the removal of the newly restored SQLcompliance and SQLcomplianceProcessing databases. Currently, the migration of the Collection Server preserves the repository databases and displays the events on the console as expected.
  • Anchor
    SQLCM-6050
    SQLCM-6050
    Resolved the issue where users were unable to register instances that are unreachable or from an untrusted domain. Currently, users can register unreachable instances or instances from untrusted domains. Please note that while unreachable instances can be registered for auditing, it is required for the Agent service to be deployed manually on these server instances.
Expand
title5.8.0 New features
  • Anchor
    SQLCM-6206
    SQLCM-6206
    The default settings for capturing DML and Select activities were changed to Extended Events on SQL Compliance Manager 5.8. This change provides a significant performance improvement for the collection service efficiency in event collection, as well as on the performance impact on monitored instances.
  • Anchor
    SQLCM-6207
    SQLCM-6207
    SQL Compliance Manager 5.8 introduces a new highly optimized index format where the application upgrades indexes in the background from a none compression state to a page-level compression type. This operation is done as an Online operation for supported SQL Server editions. Currently, the SQL Compliance Manager repository does not utilize the optimized indexes format. Rebuilding the indexes into the new optimized format provides a significant performance enhancement to the Management Console when viewing audited events and provides a considerable database repository size reduction resulting in less space usage on disk. For more information see Indexes rebuild operation. 
  • Anchor
    SQLCM-6210
    SQLCM-6210
    SQL Compliance Manager 5.8 modified the Collection Server and Agent to allow a mode where trace files are transferred by the Agent to the Collection Server without compression. Transferring files from the Agent to the Collection Server without compression provides a significant performance enhancement both on the server side in event collection efficiency, and it reduces the performance impact on the monitored instances. In the Agent Properties window, users with Agents in version 5.8 have the option to decide whether to compress or not compress the file transfer from the Agent directory to the Collection directory. For more information, see Agent Properties - Trace Options tab. 
Expand
title5.8.0 Fixed issues

There are no new features in this release.

Expand
title5.7.1 New features

There are no new features in this release.

Expand
title5.7.1 Fixed issues

General issues

  • Anchor
    SQLCM-5989
    SQLCM-5989
    Resolved the issue where the SQL Compliance Manager did not recognize a GMSA account as a Trusted user when adding the account as part of a group.
  • Anchor
    SQLCM-6058
    SQLCM-6058
    Resolved the issue which caused the cluster setup installation to perform a fresh installation instead of asking users to upgrade the agent service.
  • Anchor
    SQLCM-6128
    SQLCM-6128
    Resolved the issue where SQL Compliance Manager could not establish a connection with the AG databases on the Secondary nodes where no read access is allowed. SQL Compliance Manager successfully populates the list of AG databases to be configured for auditing on the Secondary nodes.
  • Anchor
    SQLCM-6027
    SQLCM-6027
    Resolved the issue where configuring Sensitive Column auditing caused the SQLcompliance Agent to have problems creating the sp_SQLcompliance_Audit  stored procedure.
  • Anchor
    SQLCM-6057
    SQLCM-6057
    Resolved the issue with the Daily Audit Activity Statistics Report which displayed an error message due to a missing component. The Daily Audit Activity Statistics Report runs successfully.
Expand
title5.7.0 New features

General

Supports SQL Server 2019

IDERA SQL Compliance Manager 5.7 now supports the installation of the Database Repository for the Collection Server, deployment of the SQL Compliance Manager Agent, and auditing events for SQL Server 2019. For more information, see Software requirements. 

Supports Windows Server 2019

The user can install IDERA SQL Compliance Manager 5.7 and deploy the SQL Compliance Manager Agent in Windows Server 2019. For more information, see Software requirements.  

Reports

New Reports

SQL Compliance Manager version 5.7 includes the Server Activity Report, which allows users to view the SQL Server activity at the enterprise and at the individual instance levels. With this report, users can quickly check activity in each event category audited and view statistics of the SQL Server activity. For more information, see Server Activity Report Card.

SQL Compliance Manager version 5.7 includes the Privileged/Trusted Users Report for users to list the trusted and privileged user roles set per a specific Server or Database. Users can run this report on Privileged and Trusted users to know what these were set to during a snapshot in time. For more information, see Privileged and Trusted Users Report.

SQL Compliance Manager version 5.7 includes the Sensitive Column/BAD Users Report which lists Sensitive Columns and Before-After data audit settings applied to the servers and databases in your environment. Users can run this report on Sensitive Columns and BAD auditing to know what these were set to during a snapshot in time. For more information, see Sensitive Columns and BAD Report.

Limit Report Access to specific users 

SQL Compliance Manager version 5.7 introduces the ability to restrict user access to certain SQL CM reports. As an administrator, you can grant users permission to specific reports. This way, you can tightly control permissions settings for report access for every user in your environment. For more information, see Login properties - Report Access. 

Report Filter improvements

SQL Compliance Manager version 5.7 brings updates and improvements to reports by making reports more consistent and adding new filter options, such as the ability to filter reports based on a specific schema, event type, login, or multiple logins at a time. Users can also use the time range filters to report on the exact high activity time-frames or to filter out low activity time-frames.

Expand
title5.7.0 Fixed issues

General issues

  • Anchor
    SQLCM-5505
    SQLCM-5505
    The Object Activity Report no longer renders all data on a single page, and when run, the report displays the collected data correctly. 
Expand
title5.6.1 New features

General

Sensitive Column Search

SQL Compliance Manager version 5.6.1 introduces the Sensitive Column Search functionality, allowing you to search all of the tables and columns on a targeted database to discover the sensitive data location that needs to be audited. For more information, see  Sensitive Column Search window.  

Expand
title5.6.1 Fixed issues

Installation and Configuration issues

  • Anchor
    SQLCM-5846
    SQLCM-5846
    Resolved the issue where the Stored Procedure did not get disabled for the secondary node, which caused an accumulation of trace files on the secondary node.
  • Anchor
    SQLCM-5539
    SQLCM-5539
    Resolved the issue which caused DML/SELECT filter settings to import incorrectly.
  • Anchor
    SQLCM-5514
    SQLCM-5514
    Resolved the issue where an error message appeared in the SQL Server Logs about an invalid call to stored procedure master.dbo.sp_SQLcompliance_AuditXE .
Expand
title5.6.0 New features

General

Capture Logout Events

Currently, SQL Compliance Manager captures Logins and Failed Logins; with SQL CM version 5.6, users have the ability to capture Logouts as a separate tracking option for their registered servers and for their configured Server Level Privileged Users.

Default Audit Configuration Settings

SQL Compliance Manager provides users with the capability to set up a single Server default setting and a single Database default setting. Allowing users to set up newly added Servers and Databases with their exact desired settings. Users also have the ability to apply those default settings to already registered Servers and Databases. By default, SQL CM provides users with the Idera Default Settings, which are a set of basic settings to help users start auditing from the moment a Server is registered. For more information about this feature, see Default Audit Settings

Add Databases Automatically

SQL Compliance Manager version 5.6 provides users with the ability to enable their Server Instances to automatically add any new database that is created on an audited server. For more information about this feature, see Registered SQL Server Properties - Advanced tab.

Configurations Clarifications

Compliance Manager version 5.6 improved the configurations setting to help users have a clear understanding of what is being audited at the Server level and what is being audited at the Database level. Implementing a new logic that shows items checked and unavailable for deselection at the Database level since those items are already selected at the Server level.

Info

Please note that it is possible that with the setting inheritance, you may collect more data, to avoid doing so, please review your settings to ensure that all items all collected as you expect.

Server-Level Trusted Users

SQL Compliance Manager version 5.6 allows users to configure Trusted Users at the Server level. Trusted Users designated at the Server level will apply across all databases in the selected server, giving users a greater control over who is monitored at what level. For more information, see Trusted Users at Server level.

Sensitive Columns Auditing

SQL Compliance Manager version 5.6 updated the Sensitive Column functionality in order to alert users if PII data is selected or altered. To know if such data has been accessed, users can choose to collect information for Select Only, Selects, and DML or for All Activity. 

Web Console Updates

SQL Compliance Manager version 5.6 removed all the configuration settings from the Web Console to help users have a greater control over who can change audit data while still allowing granted users to view the information being audited. Centralizing the setting configurations to the Desktop Console only, makes the Web Console a place where Auditors and Executives can easily use Reports and Alerts to see the information that they need to see.  

Anchor
SQLCM-5503
SQLCM-5503
Log File

SQL Compliance Manager version 5.6 includes a new Log file that keeps track of the product ́s versions and upgrades. The new Log file, found in the SQL CM installation folder, help users track the timelines for upgrade versions.

Anchor
SQLCM-566
SQLCM-566
Non-sysadmin

SQL Compliance Manager version 5.6 provides users with the ability to register a non-sysadmin role with permission to run the Compliance Manager Agent and permission to access the trace files.  

Anchor
SQLCM-566
SQLCM-566
Increase the number of threads processed

SQL Compliance Manager version 5.6 added the option to adjust the number of threads that can be used to process trace files at a time. 

Regulatory Guidelines

GDPR Regulation

SQL Compliance Manager version 5.6 added the General Data Protection Regulation (GDPR) guideline to the selectable list of regulatory guidelines, providing users with the option to select GDPR guideline and comply with their auditing needs. For more information about this feature, see Comply with Specific Regulations. 

Reports

Configuration Check Report

SQL Compliance Manager version 5.6 implemented the Configuration Check Report, which allows users to compare the settings configured on the registered servers and databases with the previously defined default settings. This report allows users to quickly identify where settings may vary from what is defined as the default settings as well as to identify the differences in the configurations across your registered servers and databases. For more information about this feature, see Available Reports.

Regulation Compliance Check Report

SQL Compliance Manager version 5.6 implemented the Regulation Compliance Check Report, which allows users to review the configurations set for all registered servers and databases and determine if settings comply with the selected Regulatory Guideline. This report compares the server and database configured settings to the predefined settings for any IDERA supported Regulation Guideline. For more information about this feature, see Available Reports.

Expand
title5.6.0 Fixed issues

Installation and Configuration issues

  • Anchor
    SQLCM-5526
    SQLCM-5526
    SQL Compliance Manager version 5.6 resolved the issue where the Compliance Manager Windows Console rebooted after installing or upgrading the SQL Server 2012 Native client version. 
  • Anchor
    SQLCM-3040
    SQLCM-3040
    Resolved an issue where SQL Compliance Manager recorded Create/Drop index events as “Alter User Table” events.
  • Anchor
    SQLCM-5421
    SQLCM-5421
    SQL Compliance Manager version 5.6 implemented updates in the Sensitive Column functionality which resolved the issue where Sensitive Column events were not displayed if accessed from a view.
  • Anchor
    SQLCM-5100
    SQLCM-5100
    Resolved an issue where SQL Compliance Manager was not capturing BAD auditing information when two objects with the same name exist in the same schema.
  • Anchor
    SQLCM-5317
    SQLCM-5317
    SQL Compliance Manager version 5.6 resolved the issue where SQL Statements for DDL activities was not getting captured.
  •  
    Anchor
    SQLCM-3773
    SQLCM-3773
    SQL Compliance Manager version 5.6 resolved the issue which did not allow users to remove a database from the Administration pane. 
  • Anchor
    SQLCM-4963/4974
    SQLCM-4963/4974
    Resolved an issue where users were able to register active audited databases to archived SQL Servers.
  • Anchor
    SQLCM-5239
    SQLCM-5239
    Resolved an issue where the Capture SQL statements for DDL activities and Security Changes option could not be selected unless the Database Definition (DDL) option was saved first. 
  • Anchor
    SQLCM-5104
    SQLCM-5104
    Resolved the issue where no events got captured for traces performed by non-privileged users.
  • Anchor
    SQLCM-5281
    SQLCM-5281
    Resolved the issue where using encrypted credentials to deploy SQL Compliance Manager performing a silent installation returned an authentication error message. 

  • Anchor
    SQLCM-5229
    SQLCM-5229
    Resolved the issue where SQL Compliance Manager was not able to process alerts when a Group of users is set as a Privileged User.

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 and 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 the 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 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 and above.

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.

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.4.0 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 and above.

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:

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.

Expand
title5.4.0 Fixed issues

Installation and upgrade issues

  • 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 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.
Expand
title5.3.1 New features

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.

Expand
title5.3.1 Fixed issues

There are no fixed issues in this release.

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

Expand
title5.3.0 Fixed issues

General

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

Installation

  • 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 SQL Compliance Manager Agent Service window on Windows 2012/2012 R2 installations.

Licensing

  • Anchor
    DE46199, SQLCM-2165
    DE46199, SQLCM-2165
    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

  • Anchor
    DE44606, DE44676, DE41432, SQLCM-2313, SQLCM-2448, SQLCM-2345, SQLCM-2322
    DE44606, DE44676, DE41432, SQLCM-2313, SQLCM-2448, SQLCM-2345, SQLCM-2322
    Improved the Collection Service performance to be able to process a substantially large number of trace files.

Auditing

  • Anchor
    DE43812, SQLCM-2344
    DE43812, SQLCM-2344
    SQL Compliance Manager now can log events that are accessed through a view.
  • Anchor
    DE44527, SQLCM-2316
    DE44527, SQLCM-2316
    Sensitive column traces no longer include events from databases not configured for sensitive column auditing.
  • Anchor
    DE44679, SQLCM-2312
    DE44679, SQLCM-2312
    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.
  • Anchor
    DE46329, SQLCM-2162
    DE46329, SQLCM-2162
    Exported audit settings now include database level privileged users.
Expand
title5.0.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.

Expand
title5.0.0 Fixed issues
  • Anchor
    SQLCM-2428
    SQLCM-2428
    Active Trace is now properly cleared when necessary.
  • Anchor
    SQLCM-2386
    SQLCM-2386
    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.
  • Anchor
    SQLCM-2348
    SQLCM-2348
    You can now view Reports in .CSV format.
  • Anchor
    SQLCM-3247
    SQLCM-3247
    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.
  • Anchor
    SQLCM-2401
    SQLCM-2401
    Regular user accounts are no longer able to capture SQL text used in admin activities without enabling additional options.
  • Anchor
    SQLCM-3090
    SQLCM-3090
    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.
  • Anchor
    SQLCM-2384
    SQLCM-2384
    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.
  • Anchor
    SQLCM-2350
    SQLCM-2350
    Event types 158 and 258 now include expanded details that display when these types of events occur.
  • Anchor
    SQLCM-2446
    SQLCM-2446
    SQL Compliance Manager Integrity Check now properly tracks and reports on deleted rows.



Scroll pdf ignore
Newtabfooter
aliasIDERA
urlhttp://www.idera.com
 | 
Newtabfooter
aliasProducts
urlhttps://www.idera.com/productssolutions/sqlserver
 | 
Newtabfooter
aliasPurchase
urlhttps://www.idera.com/buynow/onlinestore
 | 
Newtabfooter
aliasSupport
urlhttps://idera.secure.force.com/
 | 
Newtabfooter
aliasCommunity
urlhttp://community.idera.com
 |  
Newtabfooter
aliasResources
urlhttp://www.idera.com/resourcecentral
 | 
Newtabfooter
aliasAbout Us
urlhttp://www.idera.com/about/aboutus
 | 
Newtabfooter
aliasLegal
urlhttps://www.idera.com/legal/termsofuse

Scroll Pagebreak

...