Moving RPM to a new server and SQL Server
If you are using SQL database(s) with RPM, RPM can be moved to a new server and SQL Server if needed. Set up the new server and test it BEFORE removing access to the old server. When you are ready to go live, back up and restore your SQL database(s) and reinstall your RPM Clients from the new location to complete the move.
Before you begin, open the System Info screen under the RPM Help menu and print a copy of the report. You’ll need the Network Path from that report. This is the RPM Server folder. You also need the Version.
In the Network Path location above, open the SQLConnect application to get the list of all the RPM SQL database(s) you are using.
Install on the new server
Download and install the latest RPM version from our website to your new server.
Users must have ALL RIGHTS to the new RPM Server folder.
After installing the latest version on your new server, copy the RPMData.mdb file from the Network Path on the old server to the Network Path on the new server. This contains your RPM license information and the connection configuration to your SQL database(s).
Install one RPM Client from the new server
Install the RPM Client on at least one workstation to test RPM from this new location. This should be done on a workstation that is not using the current RPM Client, since each workstation can only have a single RPM Client installed. To install the RPM Client, run \\NewServer\RPM Server\Client Install\RPMClientSetup.exe where “NewServer” is your new RPM Server folder. Right-click on the RPMClientSetup application and select “Run as administrator” to install.
Open the new RPM Client once to upgrade to the latest version.
SQL Server test database
Create a new database on the new SQL Server for testing the connection using the instructions below.
When opening the SQLConnect application from the above instructions, the connection should be set to the new SQL Server. Use the Test button to check the connection.
If the connection is not successful, use the instructions below to test the connection to the new SQL Server.
If the connection is successful, open RPM and use the new SQL Server database you created.
Testing your existing SQL database(s)
After you have successfully set up the test database above, back up and restore your existing SQL database(s) for testing. On your old SQL Server, back up each database listed in your live SQLConnect application. On the new SQL Server, restore each of those databases. Run the script below on each of your restored databases to recreate the User ID and password you want to use for each database.
If your live RPM is not the latest version, run the upgrade script on each of your SQL database(s). Find the correct script to upgrade your existing version to the current version on the upgrade page below.
Open the SQLConnect application and enter the new Server Name for each of your databases. Enter the User ID and password you used in the “RecreateSQLRPMUser” script for each database. Click Test to check the connection for each database. If all the connections are successful, you should be able to open each company database in RPM.
Back up the latest databases from the old SQL Server and restore them all to the new SQL Server. Run the script to re-create the User ID and Password for each restored database.
Run the upgrade script for each database, if applicable.
If you are using the same databases, User IDs, and passwords as your test, you do not need to update the SQLConnect application again. Open SQLConnect and click Test for each database to confirm the connection is correct.
Open RPM using the new RPM Client to verify all the SQL databases work. Open the System Info screen under the Help menu to make sure everything is pointing to the new servers—Network Path and Data File.
Reinstall the RPM Client on all workstations or remote desktop servers by running \\New Server\RPM Server\Client Install\RPMClientSetup.exe. Open RPM following each RPM Client installation and check the System Info screen, Network Path, and Data File.