Page History

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.