Page tree

Versions Compared

Key

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

...

  • 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 an AG Listener in the Cluster Configuration Console, when naming the SQL Server instance, the underscore "_" character is not supported. 
  • Anchor
    SQLCM-6385
    SQLCM-6385
    The Audit settings Export feature does not export previously configured Server level Trusted Users. To complete the migration add the Trusted Users manually at the Server Level. 

Sensitive Column issues

  • 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-6407
    SQLCM-6407
    When you configure Sensitive Column auditing without first selecting the DML or SELECT option on the Audited Activities tab, then the SQLcompliance Agent has problems creating the sp_SQLcompliance_AuditXE stored procedure, and auditing stops working. 

Known issues in version 5.8

...

  • Anchor
    SQLCM-6273
    SQLCM-6273
    The 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
    aliasSupport
    urlhttps://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
    aliasIDERA Customer Portal
    urlhttps://idera.secure.force.com/
    .

...

  • 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, which 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 that 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 that 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-6055
    SQLCM-6055
    In SQL Compliance Manager version 5.6.1 the Row count functionality may show as “Not Applicable”. The issue occurs when you execute a large query and during execution the start and the end of the SQL Statement get captured in different trace files.  Since both events are located in different trace files, SQL CM is not able to map these events and therefore displays that Row count is “Not Applicable”. Users can increase the time of collection (default is set to 60 seconds) to capture Row count correctly.
  • Anchor
    SQLCM-6012
    SQLCM-6012
    SQL Compliance Manager is currently allowing users to select the Upgrade Agent option, even if the Agent is already in the latest version. Upon selection, SQL CM prompts you to upgrade the agent using the full setup program.
  • Anchor
    SQLCM-6027
    SQLCM-6027
    (Fixed in version 5.7.1)  When you configure Sensitive Column auditing without first selecting the DML or SELECT option on the Audited Activities tab, then the SQLcompliance Agent has problems creating the sp_SQLcompliance_Audit stored procedure, and auditing stops working.

...

  • Anchor
    SQLCM-5539
    SQLCM-5539
    (Fixed in version 5.6.1)  Import Database settings with DML/SELECT filters, 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 the 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 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. 

...