IDERA SQL Compliance Manager provides the following new features and fixed issues.
IDERA, Inc. customers have the sole responsibility to ensure their compliance with the laws and standards affecting their business. IDERA, Inc. does not represent that its products or services ensures that customer is in compliance with any law. It is the responsibility of the customer to obtain legal, accounting, or audit counsel as to the necessary business practices and actions to comply with such laws.
5.5.1 Fixed issues
Administration issues
- IDERA SQL Compliance Manager 5.5.1 process version 4.5 traces files. After upgrading the Collection Server to version 5.5.1, the agent must be upgraded to the same version. Once both the Agent and the Collection Server upgrades are complete, SQL Compliance Manager will process trace files. For more information, see Upgrade to this build.
Resolved an issue in which the SQL Compliance Manager Collection Server was not processing trace files, or was processing them slowly, causing backlog files to get accumulated in the Collection Trace Directory in large transactional databases.
IDERA SQL Compliance Manager 5.5.1 installation no longer fails if TLS 1.0 is disabled and if SQL Server 2012 Native Client is not available.
- IDERA SQL Compliance Manager 5.5.1 no longer shows the "Violation of PRIMARY KEY constraint" error nor terminates the statement when performing an archive of a highly transactional database.
Integrity check runs for archived databases performed through stored procedures.
- IDERA SQL Compliance Manager 5.5.1 installation no longer fails due to an error setting up permissions if the username used special characters (e.g. ",", space characters, etc.).
- IDERA SQL Compliance Manager 5.5.1 supports user names longer than 20 characters as well as special characters for the user's password, such as £.
For more information about new features and fixed issues in versions 5.5.x, see Previous new features and fixed issues.