SharePointTechnicalSupport

SharePoint Technical Support Blog in SharePoint Online | office 365 | azure

  • Home
  • Home
  • Solutions
    • SharePoint Server
      • SharePoint 2010
      • SharePoint 2013
      • SharePoint 2016
      • SharePoint Online
      • CU Patch Update
    • Project Server
      • Project Server 2010
      • Project Server 2013
      • Project Server 2016
      • Project Server Online
      • CU Patch Update
        • PWA2016
          • DECEMBER
        • PWA2013
      • News Project Server
    • Workflow
      • Nintex
      • SharePoint Designer
    • PowerShell
    • Windows Server
      • IIS
      • DNS
      • Active Directory
      • Windows Server 2016 Networking
    • Cloud
      • Azure
      • Office 365
  • Download
    • SharePoint Tools
    • Patch Update
      • SharePoint Patch
      • Project Server Patch
        • PWA2016
          • December
      • Office Patch
    • White Papers
    • Webinar
    • Presentation
      • SharePoint 2013 PPT
    • Video
  • MSDN Links
    • SharePoint
      • Gallery
      • Wiki
      • Forum
    • Microsoft Tech Community
    • Microsoft Docs
    • Microsoft Learn
    • Roadmap
    • Azure Update
    • SharePoint Fest
    • IIS
    • ProjectServer
      • Forum
    • Powershell Gallery
      • Powershell Forum
    • Microsoft Partner
    • sharepoint best practices
  • SPMCSE
  • Contact Me

Home › content databases › split nintex database in sharepoint

split nintex database in sharepoint

By Deviprasad Panda on 21/08/2020

split nintex database and sharepoint content database for one to one mapping of nintex and sharepoint content databases. You must be not clear, what is split database ? When nintex workflow installed in default configuration, there will be one database containing all workflow data. By time workflow content grow high which will impact performance. So as to improve performance of workflow for sharepoint site containing nintex workflow, we can move nintex database from default all in one content database to a dedicated nintex database. Moving nintex database to dedicated content database from common db is called split database.

Below is the current condition of site collection and nintex database.

Source/Old Details

Site Collection : http://win-q2repghf9du/sites/SP2019
Site Collection Content Database (multiple site collections present) : WSS_Content_8888
Nintex Database : Nintex2019
Nintex Database Server : WIN-56R9D2TBFOB

Destination/New Details

Site Collection : http://win-q2repghf9du/sites/SP2019
Site Collection Content Database (Only 1 site collection) : WSS_Content_9999
Nintex Database : Nintex2019_SP2019
Nintex Database Server : WIN-56R9D2TBFOB

Complete steps we will follow as below.

  • Create New Content Database
  • Move site collection to dedicate content database
  • Create New Nintex Workflow Content Database
  • Add service accounts to Nintex Workflow Content Database
  • Map SharePoint Content Database to Nintex Workflow Content Database
  • Reacivate Nintex workflow Site Collection feature
  • nwadmin -o movedata

Create New Content Database

  • Add a content database in sharepoint under Manage Content Database option using central admin or powershell.
New-SPContentDatabase "WSS_Content_9999" -DatabaseServer "WIN-56R9D2TBFOB" -WebApplication http://win-q2repghf9du -MaxSiteCount 1 -WarningSiteCount 0

follow the below post to get in detail information on creating new content database in SharePoint.

create add a content database in sharepoint 2019

Map permission between content database

Map or clone permission of new content database, same as the old content database (“WSS_Content_8888” and “WSS_Content_9999”).

Move site collection to dedicate content database

  • move site collection to another content database using powershell command Move-SPSite.
Move-SPSite "<Site Collection URL>" -DestinationDatabase "<Database-Name>"
Move-SPSite "http://win-q2repghf9du/sites/SP2019" -DestinationDatabase "WSS_Content_9999"

follow the complete process to move site collection to new content database from previous post link mentioned below.

move site collection to dedicate content database

Create New Nintex Workflow Content Database

  • Navigate to central admin in SharePoint.
  • Click on “Nintex Workflow Management” from left navigation central admin.
  • Click on “Database setup” present under “Nintex Workflow Management”.
  • Click on “Add content database”.
  • Enter “Database Server”, “Database name”.
  • Keep the authentication as “Windows authentication”, default recommended option.
  • For the option “Service account access” under “Grant service account access”, select “Yes”.

Add service accounts to Nintex Workflow Content Database

  • When you will select option “Service account access” under “Grant service account access”, select “Yes”, nintex service accounts will be added to the newly created content database.
  • Make sure “App pool Account” has role “WSS_Content_Application_Pools” assigned in “Database Permissions” for new nintex database “Nintex2019_SP2019”.
  • You can create ticket with db team for nintex database permissions mapping between old and new nintex databases.

Map SharePoint Content Database to Nintex Workflow Content Database

Next step in nintex database mapping, we need to map the newly created content database or dedicated SharePoint site collection content database, with nintex workflow database created newly. Follow the steps by step procedure.

  • Click on “Database Setup” present under “Nintex Workflow Management”.
  • Click on “Manage database mappings”.
  • Identify the dedicated site collection content database, we created. you will find drop down option side to content database. Select the nintex workflow content database from drop down option for mapping site collection content db with nintex workflow db.
  • Click on “OK” to apply changes.
  • It will create a connection string.

Reacivate Nintex workflow Site Collection feature

  • Navigate to the site collection where workflow data is being moved.
  • Deactivate the nintex workflow site collection feature and reactivate.
  • Save the changes and perform an IISRESET.

nwadmin -o movedata

use the command MoveData to move nintex database to new database.

  • Stop App Pool for the web application “http://win-q2repghf9du&#8221;.
  • Stop SharePoint Administration and SharePoint Timer Service in all servers in the farm.
start stop manage services in windows server with powershell
  • Open sharepoint management console and type the below command to move the nintex database to the newly created nintex database. You need to pass powershell parameter GUID of site collection. Follow the post “Get site collection GUID using powershell” to get siteid details.

Run nwadmin -o movedata, the details for which is below to move nintex workflow data Into new database

NWAdmin.exe -o MoveData [-Url <siteCollectionUrl>] [-SiteID <site GUID>] [-SourceDatabase <connection string>] [-TargetDatabase <connection string>] [-RetainSourceData]

NWAdmin.exe -o MoveData [-Url <siteCollectionUrl>] [-SiteID <site GUID>] [-SourceDatabase <Data Source=Source nintex DB server;Initial Catalog=Source/old nintex content DB;Integrated Security=True>] [-TargetDatabase <Data Source=Destination Nintex DB Server;Initial Catalog=Destination/new nintex content DB;Integrated Security=True>] [-RetainSourceData]

NWAdmin.exe -o MoveData -Url http://win-q2repghf9du/sites/SP2019 -SiteID dhajdhhh-*******-*******-*******-******* -SourceDatabase "Data Source=WIN-56R9D2TBFOB;Initial Catalog=Nintex2019;Integrated Security=True" -TargetDatabase "Data Source=WIN-56R9D2TBFOB;Initial Catalog=Nintex2019_SP2019;Integrated Security=True"
  • After running the command nintex data will be moved to new nintex DB and you will get message in powershell window as below.
Data will be moved for the site collection http://win-q2repghf9du/sites/SP2019 (site collection GUID). Restart each service to continue workflow operation.
  • Restart App Pool for the web application “http://win-q2repghf9du/&#8221;.
  • Start SharePoint Administration and SharePoint Timer Service in all servers in the farm.
  • Deactivate the nintex workflow site collection feature and reactivate that make split database activity complete .

Similar Articles

  • Nintex feature id in SharePoint
  • map crawled property to managed property sharepoint 2019
  • move site collection to dedicate content database
  • workflow could not update the item
  • SharePoint 2013 Workflow Manager possible issues and fixes

Share this:

  • Click to share on Twitter (Opens in new window)
  • Click to share on Facebook (Opens in new window)
  • Click to share on WhatsApp (Opens in new window)
  • Click to share on LinkedIn (Opens in new window)
  • Click to share on Pinterest (Opens in new window)

Related


‹ security group in active directory creation
move site collection to dedicate content database ›

Categories: content databases, Nintex Workflow, SharePoint 2019

Tags: Database setup, Grant service account accessApp pool Account, Manage Content Database, Manage database mappings, move nintex database, New Content Database, nintex database, nintex database maintenance, nintex database mapping, nintex database migration, nintex database permissions, nintex database permissions mapping, nintex database query, nintex database tables, nintex database update, nintex remove content database, nintex workflow, Nintex Workflow Content Database, Nintex workflow feature, Nintex Workflow Management, nwadmin -o movedata, restore nintex database, Service account access, sharepoint administration service, sharepoint timer service, split database, split nintex database, WSS_Content_Application_Pools

My Book

  • 1 Deviprasad Panda

Follow Me

  • YouTube
  • LinkedIn
  • Facebook
  • Twitter

Category Cloud

administration Authentication Cache content databases Default Health IIS InstallationConfiguration Migration Monitoring Performance Permission powershell powershell command powershell script Search Service Application sharepoint2010 SharePoint 2013 SharePoint 2016 SharePoint 2019 sharepoint server SharePointTools Site site collection Template web application WebPart WebService

Top Posts & Pages

  • change maximum upload file size limit in sharepoint
    change maximum upload file size limit in sharepoint
  • export import list library sites in sharepoint
    export import list library sites in sharepoint
  • configuration cache clearing sharepoint 2019 step by step
    configuration cache clearing sharepoint 2019 step by step
  • 403 forbidden error fix
    403 forbidden error fix
  • SharePoint 2019 – TCP/IP Ports
    SharePoint 2019 – TCP/IP Ports
  • Backup restore site collection sharepoint
    Backup restore site collection sharepoint
  • ViewFormPagesLockDown feature Unable to setup uniquely secured permission
    ViewFormPagesLockDown feature Unable to setup uniquely secured permission
  • user policy and permission policy level in sharepoint web application
    user policy and permission policy level in sharepoint web application

Follow Blog via Email

Enter your email address to follow this blog and receive notifications of new posts by email.

Join 775 other subscribers

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Contact Me

Bengaluru, India
support@spmcse.com
Everyday : 8 AM - 12 AM IST