The procedures in this section detail the migration steps for moving both the SQLdm Repository and the Services to a new computer. Follow each section in order for a successful migration.

SQLdm Application security is not maintained when your SQLdm installation is migrated to a new server. For more information, see Use application security to manage SQLdm.

Get a New SQLdm License Key

Because you are migrating the Repository database to a different SQL Server instance, SQLdm requires a new license key. You can easily request a new license key by sending an email to: licensing@idera.com.

To complete the request, make sure you have the name of the SQL Server instance where you plan to install the SQLdm Repository database.

Restore the SQLdm Repository on the Target Computer

For best results, use the following guidelines migrate your SQLdm Repository to the target computer:

  • Perform a full restore
  • Schedule the restore during off-hours, or times when you expect the least collection activity

To restore the Repository database:

  1. Use SQL Server Enterprise Manager or Management Studio to close any open connections to the Repository database.
  2. Use SQL Server Enterprise Manager or Management Studio to take the Repository database offline. If you cannot take the Repository database offline, stop the Collection Service.
  3. Use a tool such as Idera SQLsafe to restore the Repository database on the target server using the appropriate backup archive file.

Disable or Uninstall the SQLdm Services on the Current Computer

SQLdm Services must be uninstalled to avoid conflict with the restored SQLdm Repository. For best results, use the following procedure:

If you do not want to keep the SQLdm console on the current computer, perform the following steps:

  1. Select Start > Control Panel > Uninstall a Program on your current computer.
  2. Uninstall SQL diagnostic manager completely.

If you want to keep the SQLdm console on the current computer, perform the following steps:

  1. Select Start > Administrative Tools > Services on the current computer.
  2. Scroll down and right-click SQLdm Collection Service in the list, and select Properties.
  3. In the Startup Type drop-down list, select Disabled.
  4. Click OK.
  5. Scroll down and right click SQLdm Management Services in the list, and select Properties.
  6. In the Startup Type drop-down list, select Disabled.
  7. Click OK.

Perform a Full SQL diagnostic manager Install on the New Computer

A full install of SQL diagnostic manager installs the new SQLdm Services, link them to the restored SQLdm Repository, and install the SQLdm Console. For best results, use the following procedure for installing SQLdm:

  1. Log on with an administrator account to the computer on which you want to install the SQLdm services.
  2. Run Setup.exe in the root of the installation kit.
  3. Click SQL diagnostic manager on the Quick Start window.
  4. On the Welcome window of the setup program, click Next.
  5. Review and accept the license agreement by clicking I accept the terms in the license agreement, and then click Next.
  6. Accept the default folder for your SQLdm installation, or click Change to specify a different folder, and then click Next.
  7. Select your setup type and then click Next.
  8. Browse and select the SQL Server instance your SQLdm Repository was restored to and click Next.
  9. Enter your service account credentials and click Next.
  10. Click Install to begin installing SQLdm with the options you have selected.

Verify that the Migration was Successful

The SQLdm Console includes a system diagnostics test that allows you to test the connections of all the SQLdm components.

  1. Open the SQLdm console.
  2. Enter your new SQLdm license key.
  3. Add the SQL Server instances you want to monitor.
  4. Open the System Diagnostics utility by selecting Help > System Diagnostics.
  5. Click Test.
  6. Verify that all the tests are successful.

 

SQL Diagnostic Manager identifies and resolves SQL Server performance problems before they happen. Learn more > >
  • No labels