Versions Compared

Old Version 1

changes.mady.by.user Unknown User (6092aebacc7830006a5cfc58)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (6092aebacc7830006a5cfc58)

Saved on

Key

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

Click here for 1.0 Documentation

The following issues have been fixed and no longer represent an issue for 1.12: 

General issues 

  • SQL Elements no longer displays the message "!!! missing resource key = [com.ider....]" when the Core service goes down and actions are performed on the Instances tab.

Adding, discovering instances

  • SQL Elements now displays correctly the newly added tags when accessing the See all tags option.

Monitoring

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; however, an auto-refresh option been implemented that can be customized. Click here to configure these settings

Dashboard

  • Data from each instance and health check recommendation in the Dashboard can be refreshed. However, an additional background auto-refresh feature has been added that can be customized. Click here to configure these settings
  • The data sizes of instances that are down are taken into account in the total data size information of the Dashboard and Instance tab (with their last data collected).    

Instance details view

  • The side bar of the Instance Details view of an instance with "Unknown Error" or "Unresponsive" state now displays the latest information collected. 
  • SQL Elements now validates the correct email format of the email addresses specified to receive alert notifications. 
  • SQL Elements now displays a zero value in the Instance Details view when information such as SQL Server version, Host Server, databases, size, etc. could not be collected.   
  • SQL Elements no longer displays “No drives found” in the Computer Details of clustered instances
  • When solving an issue related to data/log at risk of running out of space, the alert no longer appears on the Health Check Recommendations section.
  • Last DBCC CHECKDB performed date in the Database Details view currently shows the correct date for new databases.
  • The user will no longer 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.
  • Discovery is not anymore only done on the local subnet. Now the user can specify the IP Addresses and Domains for the discovery job.
  • The list of discovered instances no longer includes host servers that do not have default SQL server instances.
  • Validation has now been implemented to confirm that the “domain\username” format is being used when adding new users. 
  • When refreshing health check recommendations on the dashboard, the user no longer finds that the status is not refreshed. It is now automatically refreshed.