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).
Known issues
General
- Database roles and members are not included in the Report Card Details list on registered SQL Server 2000 instances.
- The repository grooming job does not delete snapshots which are in an Error state. Snapshots in an OK or Warning state are appropriately deleted.
- Clicking Technical Support Site on the IDERA SQL Secure Quick Start window redirects to an error page.
- SMTP email configuration may not work for a secure mail server.
- The Register SQL Server error message regarding supported versions needs updating to include SQL Server 2016.
- SSRS reports do not extract to a .csv file.
- The file type of an exported policy is not selected as .xml by default. In addition, when importing a policy, the file must be manually selected by selecting All Files.
- IDERA SQL Secure displays an incomplete error message if a specific user/role is given GRANT and/or WITHGRANT permissions by one grantor, and DENY permission by another grantor. The error message does not include identifying detail about the conflicting user or role.
Installation
- Console only installations may display an incorrect message stating that the repository specified is not compatible with this version of the Console. Click OK to continue installation.
- During a new installation, the Ready to Install the Program window refers to an upgrade instead of an installation.
- Uninstalling IDERA SQL Secure does not remove the Secure folder from the registry.
- The License Agreement does not display the correct year.
Security Checks
- General Domain Accounts security check does not display results.
- The Integration Services Running security check displays as green even when the service is not running.
- The Integration Services Login Account Not Acceptable security check displays incorrect data.
- The Row-Level Security security check causes the Risk Assessment Report to display, "The following tables do not have row-level security configured: '[R7].[DB1].[Table_1]' " for registered SQL Server 2016 instances.
- The Transparent Data Encryption security check causes the Risk Assessment Report to display, "The following databases do not have transparent data encryption configured: '[R7].[ReportServer]', '[R7.[ReportServerTempDB]' " for registered SQL Server 2016 instances.
- The following security checks for Integration Services are not returning accurate information: Integration Services Login Account Not Acceptable and Integration Services Running. It is recommended that users seeking to harden Integration Services review the login account and service run status of Integration Services using the server's SQL Server Configuration Manager.
- If the Weak Password Detection security check is disabled, the Description displays a list of all the usernames that have a blank password associated with the account.
Snapshots
- When changes occur between snapshots, IDERA SQL Secure displays the change information only in the Difference column of the Snapshot Comparison window and all other columns are blank.
- Clicking the Hide and Notify when Complete button while a snapshot is in progress will hide the snapshot progress screen, but no notification is sent when the snapshot does complete.
- Taking a snapshot of an Azure SQL Database from an on-premises installation of SQL Secure may take an extended length of time. This time is decreased when the snapshot is taken from an Azure VM installation of SQL Secure.
- In the Snapshot Comparison, the difference is mentioned in reverse order. For example, "Changed from [DescriptionOld] to [DescriptionNew]" is incorrectly displayed as, "Changed from [DescriptionNew] to [DescriptionOld]."
- If a user deletes a snapshot while it is running, and then tries to take another snapshot soon after, SQL Secure may show an error message.
Previous known issues
The repository grooming job does not delete snapshots which are in an Error state. Snapshots in an OK or Warning state are appropriately deleted.
Clicking the "Hide and Notify when Complete" button while a snapshot is in progress will hide the snapshot progress screen, but no notification is sent when the snapshot does complete.
Taking a snapshot of an Azure SQL Database from an on-premises installation of SQL Secure may take an extended length of time. This time is decreased when the snapshot is taken from an Azure VM installation of SQL Secure.
The following security checks for Integration Services are not returning accurate information: Integration Services Login Account Not Acceptable and Integration Services Running. It is recommended that users seeking to harden Integration Services review the login account and service run status of Integration Services using the server's SQL Server Configuration Manager.
SQL Secure does not support SMTP servers which require SSL connections.
- IDERA SQL Secure 3.1 supports only the Active Directory Password Authentication and Active Directory Integrated Authentication modes to connect to Azure SQL database. If you are using this feature, you are responsible for setting up the VPN tunnel and any further infrastructure setup necessary for Active Directory to work those authentication modes. The VPN tunnel and infrastructure setup is not the responsibility of IDERA, Inc.
- Clicking Technical Support Site on the IDERA SQL Secure Quick Start window redirects to an error page.
- Console only installations may display an incorrect message stating that the repository specified is not compatible with this version of the Console. Click OK to continue installation.
- During a new installation, the Ready to Install the Program window refers to an upgrade instead of an installation.
- Uninstalling IDERA SQL Secure does not remove the Secure folder from the registry.
- The License Agreement does not display the correct year of 2016.
- SMTP email configuration may not work for a secure mail server.
...
SQL Secure Repository requires SQL Server 2005 or later
When upgrading, migrating, or deploying the SQL Secure Repository for the first time, ensure you select an instance running SQL Server 2005 or later for your target location. SQL Secure no longer supports SQL Server 2000 platform for the SQL Secure Repository.
...