Page History

...

• Anchor
  SQLCM-6259 SQLCM-6259

  For registered SQL Server 2019 instances, the General tab of the SQL Server Properties window displays the version as Unknown. This is only a visual issue and does not affect auditing or any other functionality.

• Anchor
  SQLCM-6283 SQLCM-6283

  During the registration of a an AG Listener in the Cluster Configuration Console, when naming the SQL Server instance, the underscore "_" character is not supported. 

...

• Anchor
  SQLCM-6277 SQLCM-6277

  Events for Sensitive Column audit data are not captured when auditing via Extended Events. When the option to capture SELECT and DML activities is configured at the server-level to capture events via the Extended Events auditing method, and the capture SELECT and DML option is not configured at database-level, but is configured to track SELECT and DML for Sensitive Column auditing. In order to capture and process Sensitive Column events correctly, change the collection method from Extended Events auditing to SQL Server Trace Files auditing.

...

• Anchor
  SQLCM-6273 SQLCM-6273

  The Installation installation wizard of the Agent service fails when running the audited SQL Server under the Local System account. In order to grant all required permissions successfully, run the SQLcompliance-x64.exe  installer to perform a manual agent-only installation.

• Anchor
  SQLCM-6230 SQLCM-6230

  (Fixed in version 5.8.1)  When performing a migration of the Collection Server, while installing the new Collection Server components, the installer raises an error message that prompts for the removal of the newly restored SQLcompliance and SQLcomplianceProcessing databases. The installer locates these databases which have been restored for the purpose of the migration, on the server instance which has been designated as the new repository database server during the installation process. Do not proceed with the removal of these databases, instead contact

  Newtablink
  alias Support url https://www.idera.com/support/supportplans

   for further assistance with installation or look up the KB Article #00012649 for further instructions, in the Solutions section for the SQL Compliance Manager product in the 

  Newtablink
  alias IDERA Customer Portal url https://idera.secure.force.com/

  .

• Anchor
  SQLCM-6247/6223 SQLCM-6247/6223

  (Fixed in version 5.8.1) When running the console reports and/or the newly SSRS deployed reports, the execution fails with the following syntax error: "Query execution failed for dataset 'ReportOutput'. (rsErrorExecutingCommand) Incorrect syntax near')'.

Known issues in version 5.7.1

...

• Anchor
  SQLCM-6219 SQLCM-6219

  (Fixed in version 5.8.1)  SQL Compliance Manager presents a security concern due to unnecessary permissions such as ALTER, EXECUTE, CONTROL, TAKE OWNERSHIP and VIEW DEFINITION, are granted to Public roles on the audit stored procedures sp_SQLcompliance_Audit and sp_SQLCompliance_StartUp .

• Anchor
  SQLCM-6073 SQLCM-6073

  When adding or editing users from the console, SQL Compliance Manager does not grant access to the Web Console Users and displays the error message "Failed to update Web Application access permission for user".

• Anchor
  SQLCM-6134 SQLCM-6134

  (Fixed in version 5.8.1)  SQL Compliance Manager encounters an issue when adding adding new users to a Windows Domain group which were previously configured as Trusted Users on a particular database. As a result these changes are not reflected in the audit configuration stored in the .bin audit file nor on the sp_SQLcompliance_Audit stored procedure. Users have to manually update the audit settings in the console for the new users to display in the audit configuration.

• Anchor
  SQLCM-6132 SQLCM-6132

  An Event Filter configured to exclude all activities recorded on the tables of a database, will not exclude DML and SELECT activities happening on columns which are not configured for Sensitive Column auditing, but which are part of a table with columns configured for Sensitive Column auditing. Event Filters are expected to exclude all activities these are configured to exclude, except DML and SELECT activities happening on columns configured for Sensitive Column auditing. This is by design.

...