Versions Compared

Old Version 1

changes.mady.by.user Nadja Pollard

Saved on

compared with

New Version 2

changes.mady.by.user Nadja Pollard

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Warning

The SQL Compliance Manager 5.0 installation kit default extraction path is the same as previous versions and may cause issues if the previous files still reside at that location. Before launching the SQL Compliance Manager 5.0 upgrade, either select a different installation location or delete the files from the following location:

c:\Program Files\Idera\SQLcompliance x64 Installation Kit or c:\Program Files (x86)\Idera\SQLcompliance x86 Installation Kit

SQL Compliance Manager 5.0 no longer supports Microsoft Windows Server 2000 or the .NET 2.0 framework 

SQL Compliance Manager 5.0 does not support Windows Server 2000 or the .NET 2.0 framework. While SQL Compliance Manager 4.5 and prior versions continue to operate with Windows Server 2000, SQL Compliance Manager 5.0 and later require the .NET 4.0 Full framework to take advantage of the additional features. For additional information about supported versions, see the SQL Compliance Manager Software requirements.

 Verify SQL Compliance Manager repository database size before upgrading

...

Known issues in version 5.0

Anchor
DE46648
DE46648
Users experience some AlwaysOn Availability Group issues when the listener uses any port other than the default

Users who change the default port for the AlwaysOn Availability Group from the default may experience the following issues. to avoid these issues, change the listener to the default port.

      • SQL Compliance Manager does not accept the name format when attempting to add the listener name using the Cluster Configuration Console.
      • If the port is not added, the agent cannot connect to the SQL Server instance. You can manually add the port to the registry setting later and it will then connect to the instance after restarting the SQLcomplianceAgent.
      • Users cannot connect to the SQL Server instance even when adding the listener with the port in the SQL CM console.
      • The Permissions Check also fails.

Anchor
DE45803
DE45803
Users receive error when installing SQL Compliance Manager after installing SQL BI if both use the same IDERA Dashboard

...

Auditing of before-after data is not supported on a limited basis for databases that use SQL Server replication

...

IDERA provides limited support for before-after data auditing of the publisher database in SQL Servers with replication. However,

...

this scenario is supported only when the publisher database with transaction replication is set to replicate data tables ONLY and no other objects. If the target database uses SQL Server replication set to replicate more than data tables, do not enable before-after auditing. Before and after data collection does not support SQL Server replication in that situation. For more information, see Microsoft Books Online for the version of SQL Server you are using.

Events statistics may not display in charts

...

IDERA WebsiteProductsPurchaseSupportCommunityAbout UsResources Legal