Attach the Nintex Workflow content databases

This section provides instructions for attaching the Nintex Workflow content databases, either to a new physical database (typical scenario) or the same physical database as the configuration database. You can add content databases gradually over time as SharePoint content databases are migrated.

The optimal mapping ratio for your environment depends on the number of SharePoint content databases in it. For guidance on mapping content databases, see Design databases and the Nintex Connect article Database Capacity Planning: Nintex Workflow. For guidance on splitting existing content databases, see Split databases.

To attach a content database to a new physical database (typical scenario)

1. In the SharePoint 2013 environment, do the following.

   1. Stop the Windows SharePoint Services Timer service.

      1. Open the Services Microsoft Management Console (MMC) snap-in.

         Note: For instructions on accessing the Services Microsoft Management Console (MMC) snap-in, see the Microsoft TechNet Library at http://technet.microsoft.com/en-us/library/cc772408.aspx.

      2. Right-click the Windows SharePoint Services Timer service and select Stop.

   2. Detach the content database.

      Note: The database must be detached before being backed up. The DetachDatabase operation stores data from the SharePoint 2013 environment that is not initially present in the content database, such as information on pending Nintex Live service requests. When the AttachDatabase operation is run in the SharePoint 2016 environment, the data is extracted from the database into the environment. If these steps are not followed, then the workflows waiting on requests for connector actions (formerly Nintex Live actions) never continue.

      1. Log on to a web application server with access to the NWAdmin tool.

         Note: For more information on the NWAdmin tool and its operations, see NWAdmin Guide.

      2. At the command prompt, navigate to the directory for the NWAdmin tool.

         The typical directory is as follows.

         C:\Program Files\Common Files\microsoft shared\Web Server Extensions\16\BIN\

      3. At the command prompt, run the DetachDatabase operation using parameters for your environment.

         For example, in the following entry, replace <myservername> with the name of your server and <mydatabasename> with the name of your database.

         NWAdmin.exe –o DetachDatabase –serverName <myservername> -databaseName <mydatabasename>

   3. Backup the database using Microsoft SQL Server Management Studio.

   4. Start the Windows SharePoint Services Timer service.

      1. Open the Services Microsoft Management Console (MMC) snap-in.

         Note: For instructions on accessing the Services Microsoft Management Console (MMC) snap-in, see the Microsoft TechNet Library at http://technet.microsoft.com/en-us/library/cc772408.aspx.

      2. Right-click the Windows SharePoint Services Timer service and select Start.

2. In the SharePoint 2016 environment, do the following.

   1. Ensure that the workflow job is stopped.

      For instructions, see Before you start.

   2. Restore the backed up database to the SharePoint 2016 location using Microsoft SQL Server Management Studio.

   3. Attach the database.

      1. Log on to a web application server with access to the NWAdmin tool.

         Note: For more information on the NWAdmin tool and its operations, see NWAdmin Guide.

      2. In SharePoint 2016 Management Shell, run the AttachDatabase operation using parameters for your environment.

         For example, in the following entry, replace <myservername> with the name of your server and <mydatabasename> with the name of your database.

         NWAdmin.exe –o AttachDatabase –serverName <myservername> –databaseName <mydatabaseName>

   4. (Optional.) Update content database parameters using the NWAdmin operation UpdateContentDatabaseParameters.

      Note: Content database parameters do not automatically migrate from Nintex Workflow 2013 to Nintex Workflow 2016.

      For instructions on setting the content database to AlwaysOn, see Set content databases to AlwaysOn.

To attach a content database that is in the same physical database as the configuration database (uncommon scenario)

1. In the SharePoint 2016 environment, log on to a web application server with access to the NWAdmin tool.

   Note: For more information on the NWAdmin tool and its operations, see NWAdmin Guide.

2. In SharePoint 2016 Management Shell, run the AttachDatabase operation using parameters for your environment.

   For example, in the following entry, replace <myservername> with the name of your server and <mydatabasename> with the name of your database.

   NWAdmin.exe –o AttachDatabase –serverName <myservername> –databaseName <mydatabaseName>