Released: Oct 25, 2025

SQL Compliance Manager v8.2 での更新項目

不具合の修正

• Query & Permission Handling Improvements
  • Resolved an issue where the SELECT query execution took longer when DML auditing was enabled on the server.
  • Fixed an issue where the SELECT Statements captured variables instead of the actual value.
  • Fixed a case where the Login Parameter in the Reports section did not display the full list of logins, preventing reports from being run with all available options.
  • Fixed an issue where newly added console users were automatically granted the 'sqlcmuser' role (full permissions), even when only read-only access was intended. Users now receive only the roles explicitly assigned to them.
  • Fixed a case where Audit Events were not visible in the SQL Compliance console for users who were part of a Windows group, even when they had the necessary permissions.
• Error Handling and UI Enhancements
  • Fixed a case that allowed users to attempt creating additional Collection Services on a machine that only had the management console installed. The message has been updated to clearly state that multiple collection servers require the SQL CM services to be installed on the machine.
  • Addressed an issue where a misleading error message was displayed during a console-only installation process.
  • Improved and clarified the wording on the SQL Compliance pane used to enter credentials when adding an Azure Blob Storage.
  • Resolved an issue where the console attempted to start the Collection Service on the repository machine when the repository was on a separate machine from the services.
  • Fixed a case where a misleading error was shown when attempting to register a reachable instance while the Collection Service was not running.
  • Fixed a bug where SQL Server 2022 (Major Engine version 16.00) was not displayed in SQL Compliance Manager. Now supports and collects audit events from RDS servers running SQL Server 2022 (Major Engine version 16.00).