Event Receivers

Hi @aporter,

Welcome to the community.
I am not sure about purging this column but my first question is how you established this column as being the root cause?
What do you define as degradation? Is it just slow navigation of the site or the running of workflows etc?

Did you look at other things such as how many items are in the list?
How many items are in the History list that the workflow uses?
How many rows are in the Nintex database workflow progress table?

These are the things that usual cause degradation.
 

Hi @aporter 
Have you solved your question? 

Hi Simon,

Thanks for your reply.

We identified this as the root cause through the following

1. Comparing with other site collections.
2. Monitoring SQL Profiler for slow queries 
3. Going deep down into the queries and identifying the root cause of the query degradation

It is important to note that this degradation is at site collection level, not at list level. So even simply by clicking on Site Settings it is taking some 4 or 5 seconds more than another site collection. And digging deeper into this we identified that there are 58k of Nintex Event Receivers registered in that site collection. These 58,000 event receivers are being loaded and processed by SP in every single request as part of the normal SP SQL calls such as when calling proc_GetTPwebMetaDataandListMetaData etc.

Further here you may find a small sample  of these 58k or more rows.

Most importantly for us before attempting any kind of fix is to understand how and when Nintex is creating these event receivers? 

And then if we can safely deregister these event receivers using PowerShell.

And how can this be avoided?

Thanks for your assistance.

Adrian