cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Not applicable

Nintex Workflow farm upgrade from 2010 to 2013, detach needed?

Jump to solution

Hi,

We are in the process of upgrading a Sharepoint 2010 (with Nintex Workflow 2010) farm to Sharepoint 2013 (with Nintex Workflow 2013) and we need to know if the detach step on the Upgrade Guide (NW2010 - 2013 Upgrade Guide.pdf) is mandatory even if we are not using Nintex Live.

This is because we will do some "test migrations" before "prod migrations" and because we need a rollback plan.

Specifically for this apparently the detach process deletes workflow history according to Nintex WorkFlow 2010 - NWAdmin Operations.pdf

DetachDatabase

Description

This operation detaches a content database from the environment. The detach process performs the following steps:

• Prepares any pending Live requests so they will not be processed in the current environment.

• Stores Live service information that will be required in the target environment.

• Unregisters the database from the environment and removes any site collection mappings that use it.

Running this command will cause workflow history to be lost from the environment. The command is intended to be run as part of the process of migrating a SharePoint database to another environment or in other scenarios where the data stored in it will no longer be required by the environment.

Labels: (1)
0 Kudos
Reply
5 Replies
Not applicable

Re: Nintex Workflow farm upgrade from 2010 to 2013, detach needed?

Jump to solution

anyone? Please?

0 Kudos
Reply
chad_austin
Nintex Newbie

Re: Nintex Workflow farm upgrade from 2010 to 2013, detach needed?

Jump to solution

Hi Andres,

The guide is highlighting the fact that the workflow history will be "disconnected" when the database is detached. You can always reattach the database and the workflow history will reappear.

I typically advise if you are not using Nintex Live to skip the detach command and simply take backups of the SQL databases to restore in the new environment. This leaves the current production farm running and allows you to complete the process without affecting users.

Just make sure that you run the dbo._PrepareForNewEnvironment stored procedure against the database before attaching it in the target farm. The stored proc removes all existing mappings and preps the database the same way the detach command does, minus saving the Nintex Live data.

Please let us know if this helps and if you have any other qustions!

Thanks,

Chad Austin

Sr. Service Engineer

Nintex

Reply
Not applicable

Re: Nintex Workflow farm upgrade from 2010 to 2013, detach needed?

Jump to solution

Hi Chad, Thanks for your answer!

One more question, do you know if the Store Procedure _PrepareForNewEnvironment is created as a result of the detach command?

Because we can not find this Store Procedure on nintex config database.

0 Kudos
Reply
Not applicable

Re: Nintex Workflow farm upgrade from 2010 to 2013, detach needed?

Jump to solution

Hi, anyone please?

0 Kudos
Reply
Not applicable

Re: Nintex Workflow farm upgrade from 2010 to 2013, detach needed?

Jump to solution

Andres,

The stored procedure "dbo._PrepareForNewEnvironment" is contained in the Nintex Workflow Config database and is created when the database was created in central admin.

You may be looking at a content database which does not contain this stored procedure.

Regards,

Andrew Beals

0 Kudos
Reply