This article provides steps on how to migrate a Patch Manager database from the Patch Manager server to a remote Microsoft SQL server.
To verify orobtain the correct version of Microsoft SQL Management Studio:
Note: Patch Manager installs Microsoft SQL Server 2005 Express Edition SP 3 (9.00.4035) by default. If you are using the default version of Microsoft SQL Server, download Microsoft SQL Server Management Studio Express SP 3 here. (© 2016 Microsoft available at https://www.microsoft.com/en-us/, obtained on May 4, 2016.)
Migration of a Patch Manager server is not a supported activity. This will require installation of a new Patch Manager server on the Windows server .
As a workaround:
All Patch Manager versions
.\EMINENTWAREdatabase instance, and then detach the Patch Manager/EminentWare database. For additional information, see this MSDN article. (© 2016 Microsoft available at https://www.microsoft.com/en-us/, obtained on May 4, 2016.)
MPKeyregistry strings on the Patch Manager server:
HKEY_LOCAL_MACHINE\SOFTWARE\EminentWare\Data Grid Service\Roles\Application, and then select Data.
MEKey, and then click Edit > Modify.
ConnectionStringregistry string on the Patch Manager server:
HKEY_LOCAL_MACHINE\SOFTWARE\EminentWare\Data Grid Service.
ConnectionString, and then click Edit > Modify.
Data Source=serverName\EMINENTWARE;Initial Catalog=EminentWare;Integrated Security=True, where
serverNameis the name of the SQL server.
DBHelper.exeon the Patch Manager server to specify the new SQL server location and credentials. The default path is:
C:\Program Files\SolarWinds\Patch Manager\Server.
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.
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.