Data Movement Options for Commerce Databases – Creation of staging database during build

You may also like...

4 Responses

  1. Giovanni says:

    greetings, excellent website, and a great understand! 1 for my favorites.

  2. Kunal says:

    Hi Ember,
    In a scenario post go-live we have 4 tiers Dev (Stage/Prod), QA (Stage/Prod), Stage and Prod. Now assuming Stage and Prod are both in-sync.
    Now if we want to sync-up the lower environments top to bottom.

    Would you recommend.

    1. Perform backup and restores from Stage to QA (Stage) to Dev (Stage). Similarly doing a backup and restore from Production to QA (Prod) and Dev (Prod). My concern is doing so we will be migrating all the transactional information from the production environment to a lower environment.

    2. Alternatively I am thinking once the QA (Staging) is refreshed from Staging we can either do a stagingcopy from QA (Staging) to QA (Prod) Or we can do a backup and restore of QA (Staging) to QA (Prod). In either case we will have to recreate the triggers again in QA (Prod).

    What is the best way to tackle this per you recommendation?

    • Ember Crooks says:

      Because there is often PII in production, usually the database to copy from is stage and not prod. In most situations, prod data should never be copied to lower environments. Backup and restore does not work with all features in the most recent releases of WCS, so as long at the database is not overly large, stagingcopy may be a good option. Whenever possible, it is best to do this in the IBM-approved direction, from prod to stage. If you do it in the other direction, you have to have the staging sequence created and you will end up with staging triggers and other objects that don’t belong in a production environment. If you’re not using WCS’s content versioning, you may be able to get away with backup/restore, but you’ll want to test it out thoroughly with a robust backout plan in case it doesn’t work.

Leave a Reply

Your email address will not be published. Required fields are marked *