Page History

...

Installation and upgrade issues

• Anchor
  Anchor
  SQLELEM-9805 SQLELEM-9805

  >>> Failing after upgrade, 9.3 GB of RAM used

  SQLELEM-9635 SQLELEM-9635

  Upgrading to SQL Inventory Manager 2.0 and later creates an IDERA Dashboard user named serviceuser with the type of Monitoring Group. AnchorSQLELEM-13548SQLELEM-13548>>> If the user changes the display name when upgrading from the SQL Inventory Manager Beta version, two versions of SQL Inventory Manager will exist.

IDERA Dashboard issues

• Anchor
  SQLELEM-13708 SQLELEM-13708

  The SQL Server Licensing widget displays an unnecessary bracket character in the # of Sockets field.

• Anchor
  SQLELEM-13561 SQLELEM-13561

  The number of discovered instances does not match in the Dashboard and the Discovered Instances tab.

Discovery issues

• SQLELEM-9629

  Anchor
  SQLELEM-9629

  SQL Inventory Manager occasionally discovers instances twice; once as part of the regular discovery process, than discovered again with the instance name as the associated port number.

  Anchor
  SQLELEM-13712 SQLELEM-13712

  SQL Inventory Manager incorrectly displays SQL Server 2012 SP3 as SQL Server 2012 SP2 in the Discovered Instances tab.

• Anchor
  SQLELEM-9671, SQLELEM-13680 SQLELEM-9671, SQLELEM-13680

  Instead of displaying only managed instances , SQL Inventory Manager on the Instances view, IDERA Dashboard displays all discovered instances in the Managed Instances tab. This tab also may display some instances that are removed from SQL Inventory Manager. AnchorSQLELEM-9633SQLELEM-9633Users may not add multiple instances when any of the instances contains a special character in the nameIDERA products.

Monitoring issues

• Anchor
  SQLELEM-9632 SQLELEM-9632

  SQL Inventory Manager fails to collect transactional activity on some databases.

• Anchor
  SQLELEM-13557 SQLELEM-13557

  SQL Inventory Manager occasionally displays the same application multiple times under different application IDs/names in the Applications list.

• Anchor
  SQLELEM-9649 SQLELEM-9649

  When a user disables monitoring for a database, the associated Health Check Recommendations update correctly, but then do not update correctly when monitoring is re-enabled even if the user attempts to restart the service.

• Anchor
  SQLELEM-13714 SQLELEM-13714

  Some users may receive an unexpected exception error when clicking Save after making a change in the Manage Health Check. AnchorSQLELEM-13686SQLELEM-13686A Guest user without the proper permissions can view the Instance Summary by manually changing the URL.

• Anchor
  SQLELEM-9614 SQLELEM-9614

  SQL Inventory Manager may display that the database consistency is not checked for some database SQL Server 2000 databases although the checks are run. An additional run of the checks does not update this value.

• Anchor
  SQLELEM-13559 SQLELEM-13559

  SQL Inventory Manager may display a foreign key constraint error message when a user attempts to edit or enter a value in some custom inventory fields.

• Anchor
  SQLELEM-9630 SQLELEM-9630

  Users who have AlwaysOn Availability Group environments may notice errors caused by the unreadable state of the secondary cluster node.

Browser issues

• AnchorSQLELEM-9619SQLELEM-9619

  SQL Inventory Manager displays unexpected error messages if the user manually changes part of the page URL to an invalid address. You can avoid this issue by changing the URL to only known, valid URL addresses. AnchorSQLELEM-13550SQLELEM-13550Browser Scan may run even when turned off.

Performance issues

...

Reporting issues

• Anchor
  SQLELEM-13710 SQLELEM-13710

  Reports exported to XML may not include the correct summary count as displayed in the PDF/XLS.

• Anchor
  SQLELEM-13709 SQLELEM-13709

  Reports exported to PDF/XLS/XML do not include the # of Cores, Core Factor, and Possible Core Licenses values.

...