First of all: Nintex published some whitepapers about this issue.
http://connect.nintex.com/files/folders/tutorials_and_how_tos_nw2010/entry20197.aspx
http://connect.nintex.com/files/folders/technical_and_white_papers_nw2010/entry17226.aspx
Based on this inputs I created a approch to move our content and Nintex Workflow databases:
Production:
- Backup SharePoint Content Database
- Backup Nintex Database
- Both have to be in Sync. No Workflow changes while Backup
Development/Integration:
- Restore SharePoint Content Database
- Delete existing Nintex Database
- Restore Nintex Database
- Mount SharePoint Database
- Perform IIS Reset
- Change license key to development key
HINT: I automated the database backup/restore process for repeating actions with
MS SQL SSIS. It allows you to prepare a package with all parameters and actions
required for the movement.
At the end you get a "click once" Nintex database deployment between farms! Quite nice..
At the end you get a "click once" Nintex database deployment between farms! Quite nice..