|
|
|
|
|
|
|
|
To prevent errors and slow workflows from overloaded content databases, we recommend regular maintenance of workflow data. To help with Workflow Data maintenance, warnings can be seen in the Health Analyzer. SharePoint's Health Analyzer will run a weekly job to scan the Nintex Content Database tables and perform a record count.
Maintenance involves monitoring workflow data, purging select workflow data when thresholds are exceeded, and rebuilding or resetting indexes as needed.
Monitor Workflow Data
A SharePoint Health Analyzer job will be scheduled to run weekly to scan the Nintex Content Database tables and perform a record count. If the table record count reaches 80% or exceeds the threshold, users can manually access a warning that will appear in Central Administration > Monitoring > Health Analyzer > Review problems and solutions page under the Performance category.
For more information, please refer to Monitor workflow data
Purge Workflow Data
When purging workflow data, purge the workflow history list before purging historic data. If you purge historic data first, then the workflow history list items cannot be purged. For more information, please refer to Manage workflow history lists
Too many records in the content database could negatively affect performance in some environments. We recommend purging historic workflow data to reduce the size of the tables and database from Nintex Administration > Purge workflow data.
For best practice, it is advised to purge the following first:
- Purge workflows from deleted list/libraries/sites.
- Purge oldest historic data.
- Purge historic data from development instances.
For more information, please refer to Purge workflow data
Rebuild or Reset Indexes
After purging workflow data, assess index fragmentation to determine if the indexes should be rebuilt or reset.
For more information, see the "Measure and reduce index fragmentation" section of the following TechNet article: Database maintenance for SharePoint 2010 Products.