Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > Migrate a local or remote Patch Manager database to a remote SQL server

Migrate a local or remote Patch Manager database to a remote SQL server

Last Updated July 23, 2018


This article provides steps on how to migrate a Patch Manager database from the Patch Manager server to a remote Microsoft SQL server.


  • Microsoft SQL Server Management Studio
  • A domain account to be assigned as the service account for the EminentWare Data Grid Server service. Initially, this account should have the SQL SysAdmin role.
  • The following Microsoft components:
    • Microsoft SQL Server Native Client 
    • Microsoft SQL Server Management Objects Collection

To verify or obtain the correct version of Microsoft SQL Management Studio:

  1. Locate your Microsoft SQL Server version. See How to determine the version, edition, and update level of SQL Server and its components for details. (© 2018 Microsoft Corporation, available at, obtained on July 23, 2018).
  2. Download the appropriate SQL Server Management Studio version.

Patch Manager installs SQL Server Express Edition by default, which has a 10GB limit. If you are using SQL Server Express Edition for your Patch Manager database, download Microsoft SQL Server Management Studio from the Microsoft website.

Migrating a Patch Manager server is not supported by SolarWinds. This procedure requires you to install a new Patch Manager server on the Windows server.

As a workaround:

  1. Install the new Patch Manager server in Evaluation mode and configure the application (except for the third party updates catalogs).
  2. Deactivate the original Patch Manager server license. This procedure moves the application to Evaluation mode, allowing you 30 days to complete the migration.
  3. Activate the new Patch Manager server.
  4. Configure the third-party updates catalogs. 


All Patch Manager versions


SolarWinds strongly recommends that you back up your registry before making any edits to your system registry. You should only edit the registry if you are experienced and confident in doing so. Using a registry editor incorrectly can cause serious issues with your operating system, which could require you to reinstall your operating system to correct them. SolarWinds cannot guarantee resolutions to any damage resulting from making registry edits.

  1. Back up your Patch Manager/EminentWare database. 
  2. Close the Patch Manager Administrator Console. 
  3. Stop the EminentWare Data Grid Server service.
  4. Open SQL Management Studio.
  5. Connect to the .\EMINENTWARE database instance and detach the Patch Manager/EminentWare database. (© 2018 Microsoft Corporation, available at, obtained on July 23, 2018.)
  6. Clear the MEKey and MPKey registry strings on the Patch Manager server:
    1. Open Registry Editor.
    2. Expand HKEY_LOCAL_MACHINE\SOFTWARE\EminentWare\Data Grid Service\Roles\Application and select Data.
    3. Select MEKey, and then click Edit > Modify.
    4. Clear the Value data field, and then click OK.
    5. Repeat this procedure for the MPKey string.
  7. Change the account used to start the EminentWare Data Grid Server service to the domain account identified in the Requirements section of this article. 

    For same domain accounts on a new server, the account can be left the same for the login tab of the service.

    1. Navigate to the Services window and make sure the EminentWare Data Grid Server service is selected.
    2. Click Action, and then select Properties.
    3. Click the Log On tab.
    4. Change the account here, and then click OK (Make sure that the account is set in the form DOMAIN\AccountName).
  8. Change the ConnectionString registry string on the Patch Manager server:
    1. Go back to Registry Editor.
    2. Select HKEY_LOCAL_MACHINE\SOFTWARE\EminentWare\Data Grid Service.
    3. Select ConnectionString, and then click Edit > Modify.
    4. Change the Value data field to address the remote SQL server.
      The default value is: 
      Data Source=<serverName>\<instance>;Initial Catalog=EminentWare;Integrated Security=True 

      IMPORTANT NOTE: <serverName> is the name of the SQL server.
      On the Source=<serverName>\<instance> there may not be an instance, you can remove the instance name but DO NOT REMOVE THE BACKSLASH:
      Example_1: Source=mysqlserver\
      Example_2: Source=mysqlserver\mysqlinstance
    5. Click OK.
  9. In SQL Management Studio, connect to the new database instance and attach the Patch Manager/EminentWare database. (© 2018 Microsoft Corporation, available at, obtained on July 23, 2018.)
  10. Run DBHelper.exe on the Patch Manager server to specify the new SQL server location and credentials.  The default path is: C:\Program Files\SolarWinds\Patch Manager\Server.
    1. Open a Command Prompt as an administrator.
    2. Change directories to C:\ProgramFiles\SolarWinds\Patch Manager\Server.
    3. Enter dbhelper.exe /s newSQLServerName\instance /p createlogins /u domainName\username /o c:\output.ini, where:

      newSQLServerName is the name of your new SQL server,

      instance is the name of your new database instance,

      domainName is the domain for the domain service account, and

      username is the username for the domain service account.

  11. Start the EminentWare Data Grid Server service.
  12. Open the Patch Manager/EminentWare console and update all of the stored credentials. See Change the account or password used for the EminentWare Data Grid Server service article and make sure to apply all the necessary updates.


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.



Last modified