When your host or ERP database moves to a new server or SQL Server version, Shipstore keeps exchanging data as long as the integration record points at the new server. Update the integration record's connection settings (server name and password) on the profile. This covers both pulling orders in and writing shipment data back out.

Before you start

  • The new server name or instance for the host database.
  • The password and any other connection details for the new server.
  • A list of the profiles and integration records that use the host database.

Steps

  1. Before cutover, go to Administration > Integrations and find each integration record used by the affected profiles.
  2. Update each integration record's connection settings with the new server name or instance and password. Or create a new integration record with the correct settings and assign it to the profile.
  3. Confirm the updated integration is the one selected on each affected profile.
  4. After the database is live on the new server, load a test order to check the inbound direction, and process a test shipment to check the outbound direction.
  5. Keep the old settings until the new server is confirmed working, then retire them.

What you should see

  • A test order loads on each affected profile after the server move.
  • Shipment data writes land in the new database table.
  • Orders and shipment data flow with no connection errors.

If something goes wrong

  • Orders stop loading after the move: the integration is still pointed at the old server, or the new connection details are wrong. Recheck the server name and password on the integration record.

Related articles

  • Recommended Server Migration Steps