- While limiting user access to specific databases or reports, selecting or deselecting checkboxes do not happen in a single click. Users must first select the database or report, and once highlighted click again to select or deselect the respective checkbox.
- 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 .
- 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".
- 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.
- 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 and DML activities happening on columns configured for Sensitive Column auditing. This is by design.