Page History

Improved Resource Usage

 SQL Compliance Manager 8.3 includes various bug fixes focused on performance and stability issues, resolves event processing inconsistencies, and improves UI terminology for greater clarity and consistency.

• Anchor
  SQLCM-6913 SQLCM-6913

  Resolved an issue where Capturing Login Events could cause excessive CPU usage.

• Anchor
  SQLCM-7151 SQLCM-7151

  SQL Compliance Manager 8.3 fixed an issue where the Collection Server trace directory could not process backlog files.

• Anchor
  SQLCM-7174 SQLCM-7174

  Fixed a case where, after upgrading SQL Compliance Manager version would populate the ObjectType column in the event repository with a value of 0 for certain event classes.

• Anchor
  SQLCM-7191 SQLCM-7191

  Updated UI terminology by changing “Collection Servers” to “Collection Services” for improved clarity and consistency.
  

  Before Image Added	After Image Added

There are no new features with this release.

Query & Permission Handling Improvements

• Anchor
  SQLCM-7008 SQLCM-7008

  Resolved an issue where the SELECT query execution took longer when DML auditing was enabled on the server.

• Anchor
  SQLCM-7113 SQLCM-7113

  SQL Compliance Manager 8.2 fixed an issue where the SELECT Statements captured variables instead of the actual value.

• Anchor
  SQLCM-7071 SQLCM-7071

  Fixed a case where the Login Parameter in the Reports section did not display the full list of logins, preventing reports from being run with all available options.

• Anchor
  SQLCM-7099 SQLCM-7099

  SQL Compliance Manager 8.2 fixed an issue where newly added console users were automatically granted the 'sqlcmuser' role (full permissions), even when only read-only access was intended. Users now receive only the roles explicitly assigned to them.

• Anchor
  SQLCM-7086 SQLCM-7086

  Fixed a case where Audit Events were not visible in the SQL Compliance console for users who were part of a Windows group, even when they had the necessary permissions.

Error Handling and UI Enhancements

• Anchor
  SQLCM-7116 SQLCM-7116

  Fixed a case that allowed users to attempt creating additional Collection Services on a machine that only had the management console installed. The message has been updated to clearly state that multiple collection servers require the SQL CM services to be installed on the machine.

• Anchor
  SQLCM-7117 SQLCM-7117

  Addressed an issue where a misleading error message was displayed during a console-only installation process.

• Anchor
  SQLCM-7123 SQLCM-7123

  Improved and clarified the wording on the SQL Compliance pane used to enter credentials when adding an Azure Blob Storage.

• Anchor
  SQLCM-7118 SQLCM-7118

  SQL Compliance Manager 8.2 resolved an issue where the console attempted to start the Collection Service on the repository machine when the repository was on a separate machine from the services.

• Anchor
  SQLCM-7121 SQLCM-7121

  Fixed a case where a misleading error was shown when attempting to register a reachable instance while the Collection Service was not running.

• Anchor
  SQLCM-6963 SQLCM-6963

  Fixed a bug where SQL Server 2022 (Major Engine version 16.00) was not displayed in SQL Compliance Manager. SQL Compliance Manager 8.2 now supports and collects audit events from RDS servers running SQL Server 2022 (Major Engine version 16.00).

There are no new features with this release.

Error Handling and System Stability

 SQL Compliance Manager 8.1 includes various bug fixes with a focus on improving error handling and overall system stability.

• Anchor
  SQLCM-6659 SQLCM-6659

  Resolved an issue where Audit Log Files were generated but not automatically removed, when auditing on premise, Azure MI, or RDS instances. 

• Anchor
  SQLCM-6758 SQLCM-6758

  SQL Compliance Manager 8.1 addressed an issue where the Agent Service failed to ship trace files when blocking events were encountered.

• Anchor
  SQLCM-6951 SQLCM-6951

  Fixed a case where the Audit Log Files would accumulate and increase in number on the audited server.

• Anchor
  SQLCM-6847 SQLCM-6847

  SQL Compliance Manager 8.1 fixed an issue where selecting Default Audit Settings while adding a new instance caused the saved Default Settings for Capture DML and Select Activities to be overwritten with Via SQL Server Audit Specifications option.

• Anchor
  SQLCM-4986 SQLCM-4986

  SQL Compliance Manager 8.0 supports the setup of multiple collection services, as shown below, to provide scale in trace file processing throughput.
  
  The method to modify the number of collection services is explained in the Multiple Collection Server service support page.

• Anchor
  SQLCM-4986 SQLCM-4986

  SQL Compliance Manager 8.0 allows the deployment of the Collection Service and Repository database on separate virtual machines. For this configuration to operate correctly, the trace directory used by the collection service must be shared and accessible by both Virtual Machines.
  Visit the Installation of Collection Service and Repository Database on Different Machines page to learn how to install the Repository Database on separate machines.