There are a few things that after I learn them, make me want to immediately share with as many people as possible. This is definitely one of those moments.
After starting a migration project where I work involving some cleanup with Nintex workflow content databases, I’ve run into something that everyone should check in their SharePoint environments right away.
It’s a setting under Central Administration for Nintex and the setting I want to warm everyone about is Automatic Database Mapping.
When you set up Nintex as a solution in SharePoint the install is pretty straight forward and not all that difficult in getting set up and going quickly.
One part of getting Nintex going after you install it is creating a config and content database to start using it to store information about the workflow history and config of the service itself in SQL.
Its at this point when you start that I recommend that you go in and turn OFF automatic database mapping.
Why am I urging you to do this so intently?
Well let’s just say I am working on a migration now with an environment that’s been using Nintex for about 3 years now, with a big config database (around 100GB or so) and multiple Nintex content databases with automatic database mapping enabled… oh and in this farm, there are about 30-40 site collections using Nintex actively.
Now at this point my main goal with this migration is to consolidate the larger Nintex sites into their own content databases.
But with automatic mapping enabled, this is going to make my job a lot harder to sort out.
Now I hope you see why this is important to do when starting at the beginning of a setup. 🙂
Here are the steps to make this change in your SharePoint setup.
Open Central Admin, and go to the Nintex section and look into the Database Management section:
Once in this section, go to the Manage area of databases down at the bottom of this section:
From here you should see the following option where you can make the change to disable automatic mapping here:
Once this is done and you click okay, then you will next need to map your existing SharePoint content databases to your existing (or even better newly created and segregated) Nintex content databases.
Just make sure that as you do this to make sure there is no active work going on for the sites you are working with. Also it wouldn’t be a bad idea to do an IISRESET as well to make sure the settings you changed take effect right away.
Trust me, doing this when you start will save you alot more time and effort than having to take a bunch of big existing databases and map them to newly created blank databases to logically separate the content out.
I hope this helps with anyone starting out with a new Nintex install or if you have to go down the cleanup road like I am as well.