Cloning

Comments

  • Id like to clone our production instance of Decisions over to our development environment. Theyre on different servers, with different connection strings and system constants, so obviously I cant just clone the entire schema and expect it to work. Is this a scenario youve dealt with before, duplicating environments while preserving connection strings and constants (and anything else that might have to be preserved)? I had thought about having a backup copy of the some of the tables in different schema so I could overwrite the dev instance with the prod one, then replace the necessary records. But the only things I know how to find in there reliably are the system constants in the entity_header_data table.

    So, got an easy way to do this? Im surely not the first person to want to do a partial clone.

  • [color=rgb(34, 34, 34)][font=Arial, Helvetica, sans-serif]That process should work. There are a couple of items you may want to do before backing up your database, however. Please see the steps below:[/font][/color]
    [color=rgb(34, 34, 34)][font=Arial, Helvetica, sans-serif]
    [/font][/color]
    [color=rgb(34, 34, 34)][font=Arial, Helvetica, sans-serif]1) Before creating a database backup, youll want to temporarily disable all of your scheduled jobs in Prod so they dont run when moving these to Dev.[/font][/color]
    [color=rgb(34, 34, 34)][font=Arial, Helvetica, sans-serif]2) Run through the process of creating a database backup of Prod and restoring it in Dev.[/font][/color]
    [color=rgb(34, 34, 34)][font=Arial, Helvetica, sans-serif]3) Re-run the Decisions installer on Dev. Make sure to check Change Settings on Update." Youll want to point your database to the restored prod database.[/font][/color]
    [color=rgb(34

Sign In or Register to comment.