Reflects the current release of Nintex for SharePoint 2016. For your version, please access assistance through the Help button in the product.
Group Nintex Workflow content databases by web application or department if your environment has 25 or more SharePoint content databases, or when your environment contains complex or high-traffic workflows. This practice helps you avoid an increased database maintenance burden by limiting the number of Nintex Workflow content databases per SharePoint content database.
In scenario C, IT uses 10 SharePoint content databases, HR uses 5, Finance uses 15, and Sales uses 12. Each department's set of SharePoint content databases is mapped to a single Nintex Workflow content database.
In this scenario, each department's set of SharePoint content databases is mapped to a single Nintex content database. For example, the 15 SharePoint content databases owned by Finance are mapped to a single Nintex content database: NW2010_Content_Finance.
Note: The illustration references typical database names for Nintex Workflow 2010; however, the illustration applies to all versions of Nintex Workflow for SharePoint.