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

11/16/2018 12:51 AM

3/22/2025 2:10 AM

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

Patch Manager

Migrate SQL DB

Note: As of now PM does not support migrating the Eminentware DB to SQL HA cluster only Standalone SQL setup is supported

Requirements 

• 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. 
2. Download the appropriate version of SQL Server Management Studio.

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. 

Steps to migrate the SQL database

SolarWinds strongly recommends backing 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 may require reinstalling your operating system to correct them. SolarWinds cannot guarantee resolutions to any damage resulting from making registry edits.

1. Open SQL Management Studio. 
2. Back up your Patch Manager/EminentWare database.
3. Close the Patch Manager Administrator Console. 
4. Stop the EminentWare Data Grid Server service.
5. Move the saved backup to the NEW SQL server and place it where you can access in the following steps.
6. Open SQL Management Studio on the NEW SQL server.
7. Restore the database backup. 
8. Add the domain admin account to the security users profile and give it SA rights and db owner.
9. 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 right click > Delete.
   4. Repeat this procedure for the MPKey string.
10. Change the account used to start the EminentWare Data Grid Server service to the domain account identified in the Requirements section of this article. 

    Note: 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).
11. 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> This 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.
12. 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.

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