When upgrading an Infor CRM cloud implementation, a staging instance is used to test any upgrades before putting them into production. When Infor creates the staging instance, they create it at the same upgrade level as the production instance, with an Infor CRM (Saleslogix) database that is a copy of the production database. The instructions Infor provides assume the customer/partner will be upgrading the provided database. It is possible, instead, to replace the provided database with a copy that has been upgraded elsewhere. This would be desirable in situations in which the cloud customer (or partner) has an upgraded copy of the database, and wishes to use that copy, rather than run an in-place upgrade on a copy of the production database. The steps for replacing the database on the cloud staging instance with an already-upgraded copy are as follows:
- Upgrade the CRM client to the same release as the upgraded database.
- In SQL, delete existing Saleslogix database. (You could save a backup copy if desired, but this shouldn’t be needed, as it is just a recent copy of production database.)
- Download a backup of the upgraded database to the staging instance.
- Restore the upgraded database, and give it the name Saleslogix. (Infor instances require the CRM database to have that name.)
- Run this SQL query against the Saleslogix database: sp_change_users_login ‘Update_One’, ‘sysdba’, ‘sysdba’ (to enable the sysdba user to work properly).
- Still in SQL, edit the SYSTEMINFO table and change the value of PINGSERVER to SALESLOGIX. (PINGSERVER is normally set to the machine name of the server, but Infor instances require it to be SALESLOGIX.)
- Verify Connection Manager and client connection can connect to the new database. Remember to cancel out of Connection Manager after successful test, otherwise it might overwrite the PINGSERVER entry.
- If necessary, modify Core Portals to point to F:\inetpub\wwwroot .
- Build and deploy.
- Staging instance is now ready for testing.
