Idera SQL Elements provides fundamental information on your SQL Servers to help you manage and keep track of your database environment without having to be an expert in Microsoft SQL Server. It gives a broad enterprise-wide view of all your SQL Servers through automated discovery as well as simple, actionable information about the state of your environment. View core information such as how many databases exist, whether they are being backed up, get access to options like availability monitoring, and notification emails so you can take action as needed.
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.
The following issues are known in version 1.1 of SQL Elements:
Known issues in version 1.2
General issues
- SQL Elements supports authentication between internal services, this feature is disabled by default. To enable it, user needs to change configuration in two places.
- When the SQL Elements Service or Core Service go down, users on the Administration tab will not be notified of the services status. They may experience error messages when trying to access any options from the Administration view.
Installation and configuration
- When uninstalling SQL Elements, the user may be prompted to close other Idera applications such as SQL Safe Management Console for example.
Adding, discovering instances
The discovery process may take into account host computers without default SQL Server instances.
- Users should take into account that if they choose WMI as a method for scanning, they may have some limitations with the number of SQL Server instances discovered. For more information on how to view and change port ranges, click here.
Monitoring
- The auto refresh option on the Instance and Explorer view may cause the option “Apply filter as it changes” to change its selected setting.
- On the Explorer tab, users may find that after selecting different options on the View Selection lists, the View list does not collapse. To solve this issue, users can manually refresh the page or change tabs and go back to the Explorer view.
Previous known issues in 1.1
General issues
- SQL Elements may display the message "!!! missing resource key = [com.ider....]" when the Core service goes down and any action is performed on the Instances tab.
- SQL Elements supports authentication between internal services, this feature is disabled by default. To enable it, user needs to change configuration in two places. Authentication mechanism may or may not work depending upon user's security policy settings.
- SQL Elements sessions do not expire anymore if users remain on the application. If they leave the application for more than thirty minutes their session will time out and users will need to log in again.
Installation and configuration
- When uninstalling SQL Elements, the user may be prompted to close other Idera applications such as SQL Safe Management Console for example.
Adding, discovering instances
- SQL Elements is currently not validating the information entered for IP addresses and DNS names. Users must be careful with the information they enter since invalid IP addresses or DNS names will cause the discovery to not work properly.
- If SQL Server instances are added using UseOleforWMI:True, IP and mac addresses may not be collected and may be shown as blank.
- When new tags are added in the Add SQL Server Instance wizard, SQL Elements may not display these newly added tags when accessing theSee all tags option.
Monitoring
General
- SQL Elements may count SQL Server instances as down until it finishes completing their initial data gathering.
- Some WMI properties in Windows XP and Windows 2003 are not available so it is possible that SQL Elements will not collect the respective information.
Explorer view
- Filters in the Explorer view only display 10 options. The user can click More to access the complete list of options. However, if the user selects options from the extended list, they may not be displayed on the initial view.
- On version 1.0, on the Explorer view, when the user filtered by tags, they could be displayed "by name" or "by count". Currently for Version 1.1 this option is not available.
Health Checks recommendations
- The Refresh option allows to get the latest information from Instances or Health Check Recommendations. When clicking this option, a request for running a background refreshing job is requested and the "Refreshing" status is displayed. This job may take some time so manual refresh is required.
- To receive alert notifications, email addresses need to be provided. The field where these email addresses are specified may not validate the correct email format.
Dashboard
- Data from each instance and health check recommendation in the Dashboard can be refreshed; however, there is no option yet to refresh all instances or recommendations at once.
- The data size of instances that are down may still be taken into account in the data size information of the Dashboard and Instance tab.
Instance details view
- The side bar of the Instance Details view of an instance with "Unknown Error" or "Unresponsive" state may not display the latest information collected.
- Information that SQL Elements was not able to collect such as SQL Server version, Host Server, databases, size, etc., may be displayed with zero value or as blank in the Instance Details view.
- SQL Elements gathers Driver information taking into account only the server hosting the instance. There is no distinction between drivers that are in a clustered resource group or not. Consequently, it is possible that in a clustered instance, SQL Elements will display "No drives found" in the Computer Details.
Previous known issues in 1.0
General
- SQL Elements does not support SQL Server 2000 instances. For more information on the supported SQL server instances, click here.
Installation and configuration
- When uninstalling SQL Elements, it may be necessary to close other SQL Server applications opened.
- An error message may be displayed when trying to install SQL Elements on a mirrored SQL Server instance. (Error -2147467259: Failed to create SQL database elem, error detail: unknown error).
Adding, discovering instances
- The Add Instance Wizard does not validate already managed SQL servers until the last step of the wizard when it tries to add it. Additionally in this version, SQL Elements may let you type any instance name without validation.
Credentials
- Users may get a “credentials failed” message with an incorrect login name on the message. They may also get this message with a blank user name when the windows account does not exist.
Monitoring
General
- SQL Server Instances with a down status may cause a discrepancy in the total instance data size and log size in the Dashboard, Explorer, and Instance view.
- It is possible that recently added instances with N/A and Authentication Failed status display a down status on the right sidebar. This is due to SQL Elements may not have completed running the initial data gathering; and therefore, it is not known yet the real status of those instances.
- The user may experience the following message in the Administration tab: "!!! missing resource message key=[com.idera.common.rest.RestException: An exception occurred getting the product configuration.] args=[]”, when Idera core/elements services are down.
Explorer view
- The Explorer view may let users apply filters for instances that are down.
- On the Explorer view when filtering by tags, the total data size may take into account instances more than once for those ones that are linked to different tags.
Health Check Recommendations
- Health check recommendation “Volume at risk” may duplicate the number of recommendations per instance belonging to the same volume.