Page History

IDERA strives to ensure our products provide quality solutions for your SQL Server needs. If you need further assistance with any issue, please contact IDERA Product Support (www.idera.com/support).

4.4 Known issues

...

• Anchor
  SQLSECU-23092926 SQLSECU-2309

  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.

  2926

  When the server is moved from one policy to another, the Schedule settings are not updated to the new policy schedule. This issue can be solved by manually editing the server or policy schedule.

• Anchor
  SQLSECU-21512935 SQLSECU-2151

  The uninstall process may not completely remove the SQL Secure folder in the Program files but user can manually remove it after uninstall process completes. AnchorSQLSECU-2083SQLSECU-2083The Snapshot Data Collection process for Windows Server 2016 is showing some incorrect warnings. AnchorSQLSECU-2064SQLSECU-2064 SQl Secure is not able to add new servers to Server Group Tags. AnchorSQLSECU-2037SQLSECU-2037The Show Risk Only option in the Risk Assessment Report does not make any difference in the report list. AnchorSQLSECU-2065SQLSECU-2065The Register SQL Server error message regarding supported versions needs updating to include SQL Server 2017.

Security Checks

...

Previous known issues

General

...

Installation

...

Security Checks

...

• 2935

  SQL Secure 4.4 is unable to take snapshots from Azure Databases instances.

...

Snapshots

...