Page tree

Versions Compared

Key

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

...

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

...

  • Anchor
    SQLCM-5989
    SQLCM-5989
    (Fixed in version 5.7.1)  When users add a GMSA account as part of a group, SQL CM does not recognize it as a Trusted User. As a workaround, users need to specify the account and the group when configuring Trusted Users and update the audit settings each time a new GMSA account is added to the group.
  • Anchor
    SQLCM-6058
    SQLCM-6058
    (Fixed in version 5.7.1)  When users run the SQLcomplianceClusterSetup.exe to upgrade agent service deployment to 5.6.1, the cluster setup installation does not prompt user users to agree to upgrade and instead it performs a fresh installation.
  • Anchor
    SQLCM-6128
    SQLCM-6128
    (Fixed in version 5.7.1)  When registering databases to the Primary node of an audited Availability Group, SQL Compliance Manager is not able to establish a connection with the AG databases on the Secondary nodes. Therefore, these databases do not get automatically register on the Secondary nodes.

...

  • Anchor
    SQLCM-5539
    SQLCM-5539
    (Fixed in version 5.6.1)  Import Database settings with DML/SELECT filters, flips flip import settings. When users import database audit settings and apply those settings to multiple databases, the imported settings apply only to some databases. If user imports and applies the audit settings to the same databases again, the configuration settings get flipped, applying the import settings to the databases it did not apply to before while deleting the settings from the ones it previously applied them to.
  • Anchor
    SQLCM-5514
    SQLCM-5514
    (Fixed in version 5.6.1)  Invalid stored procedures call to sp_SQLcompliance_AuditXE. A message about an invalid stored procedure appears in the SQL Server Logs; "Could not find stored procedure master.dbo.sp_SQLcompliance_AuditXE". The error message appears because no stored procedure with the name "master.dob.sp_SQLcompliance_AuditXE" exists. 
  • Anchor
    SQLCM-5505
    SQLCM-5505
    (Fixed in version 5.7) SQL Compliance Manager Object Activity Report renders all data on a single page. When the Object Activity Report is run, the report displays all the collected data in on a single page. 
  • Anchor
    SQLCM-5846
    SQLCM-5846
    (Fixed in version 5.6.1) SQL Compliance Manager traces are getting collected on the Passive nodes of an Availability Group. When a primary node becomes a secondary node, the Stored Procedure does not get disabled for the secondary node and the trace files keep gathering. This causes an accumulation of trace files on the secondary node. 

...

  • Anchor
    SQLCM-5526
    SQLCM-5526
    (Fixed in version 5.6)  Installation or upgrade of SQL Server 2012 native client may cause the system to reboot. When installing or upgrading the version of the native client, once the process is complete, a system reboot occurs without a previous warning. 
  • Anchor
    SQLCM-4831
    SQLCM-4831
    IDERA Dashboard 3.0.3 and later does not support SQL Server 2005 SP1. Users should not attempt to install SQL Compliance Manager with IDERA Dashboard 3.0.3 and later on a SQL Server 2005 SP1 as that version of SQL Server is not supported by IDERA  Dashboard.

...