Collect All -- Timing out on Large Assignment Pools

Topics: Developer Forum, Project Management Forum, User Forum
Feb 3, 2011 at 3:52 PM

WSS 3.0 SP2 with SLK 1.3.1

We have a number of assignments that need to be retracted for a time that we are having issues using the collect all feature of SLK.  These assignments have 1000-2000 users assigned to them and SLK basically crashes trying to collect them.  It eventually times out, but for a period of time, SLK is unusable for everyone.  After it times out, it does not actually collect anything.

Anyone have any ideas on how to mass-collect assignments on assignments with a large number of assignees?

Is there a flag in the database that you can just run an update script against?

Any help is appreciated

--Chris

Coordinator
Feb 10, 2011 at 10:37 AM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
Coordinator
Feb 10, 2011 at 10:40 AM

Hi Chris,

Thanks for the report. I've done some digging and found out that when you Collect All SLK start a serializable transaction then issues 6 commands per user to the database. So you've got 6000-1200 database commands which leads to the timeout. As it's updating the core tables, the serializable transaction basically locks them preventing anyone else from using them. And when it timeouts the transaction rolls it back.

Conceptually this should be able to be done as a simple bulk update, so I'll have to investigate and fix.

Richard

SLK Coordinator

http://blog.salamandersoft.co.uk