TOPICHow to move or split workflow information to a new content database.
- Sign into one of the SharePoint servers with a farm account (account that has full access to each workflow database). If needed create the new database where workflow data will be moved.
- Backup databases involved in data move.
- Collect the full connection strings for both the "source database" and the "target database". For example: Data Source=MyDatabaseServerName;Initial Catalog=MyDatabaseName;Integrated Security=True
- Navigate to Nintex Workflow Management > Database Setup > Manage database mappings.
- Update the database mapping so that it reflects the new database configuration.
- Navigate to the site collection where workflow data is being moved.
- De-activate/re-activate the Nintex Workflow Site Collection features to update the database mapping.
- Stop the Workflow Timer Service within the SharePoint farm.
- Stop the IIS Site where workflow data is being moved.
- Open a SharePoint Management Shell and run the following command:
NWAdmin.exe -o MoveData -Url <siteCollectionUrl> -SourceDatabase <connection string> -TargetDatabase <connection string>
For example: NWAdmin.exe -o MoveData -Url http://workflow2013testing.nintexsupport.com -SourceDatabase "Data Source=WorkflowDatabaseServer;Initial Catalog=NintexConfigurationDatabase;Integrated Security=True" -TargetDatabase "Data Source=WorkflowDatabaseServer;Initial Catalog=NintexContentDatabase2;Integrated Security=True"
- Start the IIS site and Workflow Timer Service again.
2. After the data is moved, the source content database must remain in place until the redirects added by the MoveData operation have been cleaned up. To clean up redirects, use the CleanTaskDirects operation.
3. This moves historic data for the workflows which only have workflow progress data.
For more information on using NWAdmin, see the Nintex NWAdmin Operations Guide.