Released: Apr 19, 2022

Actualizaciones en v5.9

Características

Performance Enhancements

• Collection service multithread event file capture processing:
  • Improved event file capturing mechanism by enabling parallel processing.
  • Previously several areas appeared to be functioning as single-threaded. With this release, the Collection Service can now process multiple files simultaneously.
  • This change enhances the performance and scalability of SQL Compliance Manager and significantly lowers the impact on the monitored systems while maintaining data integrity.
• Console application performance improvements:
  • Improved the console application response state to avoid and eliminate areas that caused "Non-Responding" conditions.
  • Improved the console application's response time by streamlining the SQL Compliance Manager index structure and query efficiency.
  • These enhancements reduce latencies and improve the overall usability of the SQL Compliance Manager console.
• Improved reports and console performance for large repositories by modifying the repository index structure and query efficiency to refine console application response time.
• Inheritance mechanism adjustments:
  • This release introduces a simplified inheritance mechanism by providing users with flexible customization options when configuring audit activities settings for both Server-Level and Database-Level settings.
  • In this release, whenever Privileged Users are set on the Server-Level, they are automatically displayed on the Database-Level.

Alerts

• Timeframe configuration:
  • Alert Rule wizard now includes new timeframe configuration feature.
  • Added new screen to the Alert Rule wizard where users can decide to keep an alert rule active within a specified time and for a specific number of days.
  • Added the ability to limit the number of notification alerts sent via email.

Correcciones

• Exporting Audit Settings now successfully includes an export of the Server Level Trusted Users configured.
• Resolved the issue where the SQL Server Properties window displayed the version as Unknown for registered SQL Server 2019 instances. Now, the correct version is shown.
• Resolved the issue where auditing stopped working when a user-configured Sensitive Column auditing without first selecting the DML or SELECT option caused the SQLcompliance Agent to have problems creating the sp_SQLcompliance_AuditXE stored procedure.
• Resolved the issue and now events get captured for sensitive columns when Select and DML are enabled at the database level Audited activities on fresh and upgraded setups.
• The DML Activity (Before-After) report shows accurate results regardless of the collection method being set to Extended Events or SQL Tracing.
• The DML\SELECT filters are now working correctly when auditing SQL Server 2019 and no longer prevent DML and SELECT activities from being audited accordingly.
• The following error is no longer observed when attempting to run DML changes on a table configured for Before-After auditing in the software. "The DELETE permission was denied on the object 'SQLcompliance_Changed_Data_Table'."
• The retention period of the Activity Log is now configurable. It is set to a default of 60 days which can be modified in the SQLcomplianceCollectionService.exe.config file, in the MAX_ACTIVITY_LOGS_AGE flag.
• Console loading times are faster now at both console startup and when navigating to the Audit Events view of the audited server or database.
• Event details on INSERT and DELETE events, audited not as INSERT INTO or DELETE FROM executions, are no longer missing the Target Object Name information, showing the name of the database object affected by the audited DML change.
• Reports deployed to SQL Server Reporting Services now show corresponding logins in the Login dropdown filter when these are set to run against an archived database.
• Reports no longer show a syntax error when executed either from the console application or SQL Server Reporting Services.
• The permissions check for the SQL Server service account permissions on the Agent Trace Files folder no longer fails when the SQL Server is running under the NETWORK SERVICE service account.
• Data types have been updated in the tables saving Before-After data to prevent the tables from filling up with event data too soon. This would have prevented new events from processing otherwise, as a result.
• The console application logging is no longer showing a collation conflict error, as shown below: "Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.".