Stage copy utility and the production database

The Stage Copy utility allows an administrator to copy data from the production database to the staging database. The Stage Copy utility should only be used in specific administrative situations, such as setting up a new staging server or recovery from a corrupt staging server database.

The Stage Copy utility ensures that the production and staging databases are synchronized. After the Stage Copy utility runs successfully, the database tables managed by the staging server should never be updated on the production database. You should update these tables on the staging server then use the Stage Propagate utility to propagate the changes to the production database. Updating staging server-managed tables on the production database will likely fail due to a potential key conflict or reference integrity violation. If you must update the staging server-managed tables in the production server database, you must use the Stage Copy utility to synchronize the staging and production databases.

To guarantee that the staging server-managed tables are never updated on the production database, the tables must be under the control of a Site Administrator only. In some cases, the staging tables in your production database are updated by an individual customer or merchant after the data has been copied using Staging Copy. For example, you cannot prohibit a merchant from modifying the OFFER table in the production database after copying to the production database. In this situation the OFFER table cannot be managed by the staging server.

Feedback