IDERA strives to ensure our products provide quality solutions for your SQL Server needs. The following known issues are described in this section. If you need further assistance with any issue, visit the Support Portal at idera.force.com
After upgrading the IDERA Dashboard with the BI 2.1 installer, SQLDM 10.0.2 installations fail to sync new users’ permissions with the web console. This issue affects only users created in the SQLDM desktop console after the upgrade.
The suggested workaround is as follows:
The suggested workarounds are as follows:
Upgrade SQL Diagnostic Manager to version 9.1 before install.
Install BI Manager 2.1 on a separate dashboard.
Upgrade the current dashboard to version 2.1.1 before install.
Adding BI Instances
After adding an instance to SQL BI Manager with the required credentials for SQL Server and WMI connections, and attempting to "Test Credentials", BI Manager fails to connect with the instance and displays the following error message:
"The following error occurred while connecting to instance XXXXX: The following system error occurred: No such host is known. , with olap-connection. This prevents the collection of SSAS Cubes, Sessions & Objects"
This is caused by the application not being able to support instances with UDP (User Defined Port) configuration.
SQL BI Manager 1.0 users first must upgrade to SQL BM Manager 1.1 before upgrading to version 1.5.
To upgrade from SQL BI Manager 1.0 to version 1.1, follow these steps:
To upgrade from SQL BI Manager 1.1 to version 1.5, see Install SQL Business Intelligence Manager.
The IDERA Dashboard installer is designed to create a login for the specified service account in the SQL Server Repository database. However, this installer is occasionally unable to create a login on SQL Server 2005 Repository databases. This results in lack of access to the IDERA Dashboard Repository. To solve this issue, create the necessary SQL Server logins outside of the installation process:
In SQL BI Manager 1.1 migration occurs as part of the installation process and requires a custom upgrade procedure. This limitation will be corrected in an upcoming release.
To upgrade from SQL BI Manager 1.0 to our latest version follow these steps:
In SQL BI Manager 1.0, any BI service must have a local instance of SQL Server installed to be registered for monitoring. For machines where a BI service is running without a local SQL Server instance, installing a copy of SQL Server Express on the target machine allows those services to be monitored. This limitation will be corrected in an upcoming release.
Users that want to stop monitoring a specific BI service should use “Disable Monitoring” which is accessible through the “gear” icon to the right of the service instance name in the service (SSAS, SSRS, SSIS) view. Selecting Remove will remove the service instance and any associated monitored BI services will stop collecting data and sending alerts as a result.
SQL BI Manager is designed to add users and grant access as needed. However, users that lack an account on the local SQL BI Core Repository fail to be added as new users in the Administration tab. Please register new users with the SQL BI Core Repository before adding them to SQL BI Manager.
Some recently added users may experience issues when login in the SQL BI Manager console regardless of their Administration or Read Only privileges, or correct Windows credentials. An incorrect user name or password message displays. This is a result of the above requirement to register new users with the SQL BI Core Repository before adding them to SQL BI Manager.
Windows Service First Session Requests/sec and Snapshot Updates/sec are not available for SQL Server 2008 in the SSRS performance view.
Users may find that occasionally the CPU Usage Percent values for the SSAS, SSRS, and SSIS roll up views of the main dashboard are incorrect.
SQL BI Manager is designed to display and report on database cube information for SQL Server Analysis Services. However, an issue in the SSAS Performance view results in an empty view for the x86 version of SQL Server 2008.
Cache: <Inserts/sec, Evictions/sec, KB added/sec>
Processing: Rows Written/sec
Processing Aggregations: Rows Created/sec
Processing Indexes: Rows/sec
Storage Engine: Data Read from Data File
Storage Engine: Dimension Cache <lookups/sec, hits/sec>
Storage Engine: Flat Cache <lookups/sec, hits/sec>
Storage Engine: Measure Group Cache <lookups/sec, hits/sec>
Storage Engine: Calculation Cache <lookups/sec, hits/sec>
Threads: Processing Pool Job Queue Length
Cache Flushes/Sec
Delivers/Sec
Events/Sec
Snapshot Updates/Sec
Total App Domain Recycles
Charts in the SSAS, SSRS, and SSIS performance views display metric data only in the 'Minutes' scale. Scale drop down options for Hour, Day, Week, and Month are not available in this release.
For this release users should be aware that the information displayed at the top right in the DASHBOARD view (UP, DOWN, CRITICAL) encompasses the total number of monitored BI Service Instances and may be different than the number of monitored servers.
For this release users should be aware that when using the option to Disable Monitoring, available in the SSAS, SSRS, and SSIS performance views, only the specific BI service is disabled. This information is reflected in MY ENVIRONMENT under "Disabled Instances" from the DASHBOARD VIEW.
SQL BI Manager is designed to collect data and set alerts every 6 minutes. Displayed data may be manually refreshed by selecting F5.
SQL BI Manager displays by default 10 rows in the different widget sections of the main dashboard. It is not possible to modify this value in this version.
| IDERA Website | Products | Purchase | Support | Community | About Us | Resources | Legal |
|---|