Versions Compared

Old Version 16

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

Saved on

compared with

New Version 17

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

Saved on

Key

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

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 , please contact Support (www.idera.com/support).

Known issues for 8.0

  • To upgrade from build 8.0.0.423 to Hotfix build (8.0.0.503) users need to follow these steps:
    • Use the installer to prompt the upgrade
    • Type the credentials for the newly created SQLsafe REST service
    • When upgrading the instance of SQL Safe, take into account the value to be added to the location property.
    • Access the web application. When an "exception" message is displayed, select the option "Redirect me to Dashboard."
    • Go to the Administration tab of the Idera Dashboard, select Manage Products, and edit the respective SQL Safe instance. In the Location field, add the value specified during installation. 
    • Restart the IderaDashboardCoreService (Automatically the IderaDashboardWebAppService service is restarted.)
  • After registration, SQL Safe Web Console will list all available instances in your repository. Users have to use the options to Bulk Edit credentials to change credentials for those instances they are not able to monitor.
  • Users should take into account that time fields for the Policies, Operation History, and Databases tabs in the SQL Safe Web Console are currently expressed in the GMT time zone.  
  • The Progress bar of the Operation History tab in the SQL Safe Web Console does not update its progress during the operation execution.
  • When uninstalling SQL Safe, users may need to reboot their computers to remove the SQLvdb Filter Service. 
  • The SQL Safe Web Console is not currently sending e-mail notifications for Restore Operations. 
  • When uninstalling SQL Safe, users should manually remove the product from their Idera Dashboard before rebooting their system. 
  • The Collection Service is set to run as Local System by default. Users should ensure this account has sysadmin rights in the SQL Server instance hosting the repository.  
  • Users who plan to install Safe 8.0 on the same system as VDB should obtain the VDB 2.1 buddy drop which addresses compatibility issues between the two products. Please contact Idera Support for more information. 
  • After installing SQL Safe, existing virtual databases may not be accessible. Idera recommends to first upgrade with the VDB 2.1 buddy drop, unmount virtual databases, install SQL Safe, and then recreate the respective VDBs. Contact Idera Support for more information. 

...