Reflects the current release of Nintex for SharePoint 2016. For your version, please access assistance through the Help button in the product.
Map content databases
Applies to NintexWorkflow only
This topic describes how to map NintexWorkflow content databases to SharePoint content databases.
Each SharePoint content database corresponding to site collections using NintexWorkflow must be mapped to a NintexWorkflow content database. The NintexWorkflow content database that you map to a given SharePoint content database affects all site collections within that SharePoint content database. The mapping you specify is applied when the NintexWorkflow feature is activated on site collections within the SharePoint content database. Changing the mapping affects new site collections only; original mapping is retained for existing site collections in the SharePoint content database.
To change the mapping for existing site collections on a given SharePoint content database, use the NWAdmin operation MoveData. This operation moves existing workflow progress data to a different NintexWorkflow content database. Using this operation is helpful when you want to keep all site collection data together.
For instructions on how to implement a 1-to-1 mapping for an existing site collection already using Nintex Workflow, see Split databases.
For more information on the MoveData operation, see NWAdmin Guide.
All data generated from a given site collection is stored within the mapped NintexWorkflow content database. By default (if automatic mapping is enabled), when a workflow is first run on a site collection, a content database is selected automatically based on how many site collections it already contains.
When each mapped NintexWorkflow content database is specified, its connection string is configured. Properties of the connection string include the SQL Server database server, the database name, and the authentication settings.
Using multiple content databases helps spread the load for environments with complex or high-traffic workflows running on multiple SharePoint content databases. In small farm scenarios it is reasonable to use the same database for the content and configuration databases.
To access your database mappings
Access the Database management page: On the Central Administration Home page, click Nintex Administration and then click Database management under Licensing and setup.
On the Database management page, click Manage database mappings.
The Manage database mappings page appears. See Manage database mappings page. SharePoint content databases appear in the list view. From the list, you can map each database to an existing or new content database.
To map workflow content databases
Access the Manage database mappings page using the procedure above.
Enable automatic database mapping (recommended).
In the Allow automatic mapping of Nintex Workflow Content Databases option, select Yes. When disabled, you must select a content database for each mapping.
Map the SharePoint content databases to your NintexWorkflow content databases as follows:
To map a SharePoint content database to an existing NintexWorkflow content database, select the database from the drop-down list under Map to Workflow Content Database.
To map a SharePoint content database to a new content database, do the following:
Select Add content database from the drop-down list under Map to Workflow Content Database to display the Add content database page. See Add content database page.
On the Add content database page, enter the database server, name, and other settings.
Click OK to go back to the Manage database mappings page. The added content database is mapped.
Considerations