Skip to main content
Nintex Community Menu Bar
Solved

NINTEX Content DB tables approaching threshold

  • April 20, 2023
  • 1 reply
  • 597 views
  • Translate

Forum|alt.badge.img+2

I see this message on the Central Admin of our on-prem farm.

 

Workflow data maintenance required to avoid workflow performance degradation.
Nintex Content DBs impacted:

NintexWorkflow2013DB
WorkflowProgress table has reached 84% of the threshold (8383188/10000000)

 

Instructions on the link provided are unclear to me.

Thanks for any help.

Best answer by SimonMuntz

HI,

 

Is there something in particular in the instructions that are not clear?

A high level overview of the process is to purge the SharePoint history list data and then purge the same data from the Nintex content database. Ie purge all data prior to 2021 for all history lists and in the Nintex content database.
Nintex provided the NWAdmin tool to help with the purging.

 

Note that the 10 million figure is not a hard figure.  It depends on the environment such as how many servers are in the farm and the processing power of those servers. How many users and how many workflows are running.  Some farms can get up to 300 million rows and have no issues until they hit 301 million rows.  In saying that, SharePoint should not be used for storage and that is why history lists need to be maintained.

View original
Did this topic help you find an answer to your question?

1 reply

SimonMuntz
Nintex Employee
Forum|alt.badge.img+22
  • Nintex Employee
  • 2465 replies
  • Answer
  • April 26, 2023

HI,

 

Is there something in particular in the instructions that are not clear?

A high level overview of the process is to purge the SharePoint history list data and then purge the same data from the Nintex content database. Ie purge all data prior to 2021 for all history lists and in the Nintex content database.
Nintex provided the NWAdmin tool to help with the purging.

 

Note that the 10 million figure is not a hard figure.  It depends on the environment such as how many servers are in the farm and the processing power of those servers. How many users and how many workflows are running.  Some farms can get up to 300 million rows and have no issues until they hit 301 million rows.  In saying that, SharePoint should not be used for storage and that is why history lists need to be maintained.

Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings