Idera SQL Elements provides fundamental information on your SQL Servers to help you keep track of and manage 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 this version of SQL Elements:
Known issues in version 1.0
General
- SQL Elements does not support SQL Server 2000 instances. For more information on the supported SQL server instances, click here.
- Discovery is only done on the local subnet.
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.
- The list of discovered instances may include host servers that do not have default SQL server instances.
- The user may find the following message: ‘Failed to process setAttr Failure (NS_ERROR_FAILURE)’ when adding SQL Server instances in Mozilla Firefox 24.0 and Internet Explorer 8.
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.
Users
- Users added to SQL Elements must be Active Directory users and names should be added in the format “ domain\username”. However, there is no validation yet that confirms users are actually Active Directory users.
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
- When refreshing health check recommendations on the dashboard, the user may find that the status is not refreshed until the page is manually refreshed.
- Health check recommendation “Volume at risk” may duplicate the number of recommendations per instance belonging to the same volume.
- User may find that after solving an issue related to data/log at risk being to full soon, the alert may still be appearing on the Health Check Recommendations section.
- Last DBCC CHECKDB performed date in the Database Details view may not show the correct date for new databases.