Moving RPM to a new SQL Server
If you are using SQL database(s) with RPM, RPM can be moved to a new 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) to complete the move.
Prerequisites
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.
In the Network Path location above, open the SQLConnect application to get the list of all the RPM SQL database(s) you are using.
Testing your existing SQL database(s)
You will need to 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.
Next, test your SQL server connection following the instructions below.
Testing the RPM SQL server connection
Important: Make sure no one is using the live RPM application while the following testing is performed. 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.
After the test is completed successfully, make sure to return the connection information to its previous state.
Go live!
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.
Open SQLConnect and update to the new SQL server. Click Test for each database to confirm the connection is correct.
Open RPM to verify all the SQL databases work. Open the System Info screen under the Help menu to make sure the Data File path is pointing to the new server.
Upon opening the RPM application, the connection to the new SQL server should complete automatically. If not, or if any errors occur, you may need to run the Refresh Client utility on all affected workstations.