IDERA strives to ensure our products provide quality solutions for your SQL Server needs. If you need further assistance with any issue, please contact Support (www.idera.com/support).
SQL Secure only recognizes the first license key added. If the first license key gets expired the product will ask for a new valid license key, even if the product has another valid license keys registered. You can remove the old license key by deleting it and this way it will recognize the valid license key. You can contact your IDERA Account Team for an updated license.The User Permission Report for specific databases may generate timeout error. Increase the SQL Command Timeout from default to fix the problem.
The uninstall process may not completely remove the SQL Secure folder in the Program files but user can manually remove it after uninstall process completesCIS for SQL Server 2016 policy is not listing the 3.10 (Ensure Windows local groups are not SQL Logins) and the 3.11 (Ensure the public rolw in the msdb databases is not granted access to SQl Agent proxies) security checks.
The Snapshot Data Collection process for Windows Server 2016 is showing some incorrect warningsComparison Report is not showing server role changes.
SQl Secure is not able to add new servers to Server Group Tags.
|Anchor||SQLSECU-2037||SQLSECU-2037The Show Risk Only option in the Risk Assessment Report does not make any difference in the report listThe User Permission Report is missing some information when exporting in Excel files.|
|Scroll PDF Exporter Ignore|
SQL Secure sees who has access to what and how permissions are granted in SQL Server.