We have 350k+ records and do experience slowness - especially when everyone is trying to clock out for break at the same time.  I have Work Orders archived down to 3 years but have WOLABOR records still in the table from the beginning of 2010.  Not sure how that relates to your table size?

We have 5 years of WO records.  Our WOLABOR has 180k records going back to 2002.  We are now experiencing a complete hang up..  I'm considering a roll back to the prior version of the program, but am concerned about a selective rollback not populating all the required tables.

Thank you.  Refresh my memory, do I need everyone out of the system to archive and re-index?

It gets hard when we're running two shifts and people are clocked in nearly around the clock.  The opportunities to kick everyone out are few and far between.
 
Thanks for the help.

Reindexing was completed with the Archive process (done once a year in February).  Our BKDCPLAB table is empty at the end of EVERY day.  I check it as I have to clear out invalid 'employee' records (0 employee from HH-F and 1/10/100 employee from DC-A .... our codes are 10XX).  The delay is about 5 seconds during 'random' scanning, but can be 30+ seconds when everyone is scanning out for break at the same time.

Even though DC-A is saving to BKDCPLAB it turns out it is doing a scan through WOLABOR to recalculate the quantity complete for the operation in question.  It is an indexed search so it should not be taking a noticeable amount of time unless you have a large number of records on a single operation which may be Dawn's case as she is using a single work order for everybody to clock break time.  If the Break Time work order is defined as a Status I (Indirect) which it should be, we can easily change the program to ignore the recalculation for status I WO.  Tony, we need more details as to the particulars of your situation.

Archiving WO clears the WOLABOR records assuming the work orders are closed so I don't know why you have so many old entries.  We are changing the program not to do the scan for Status I work order which is what the generic "catch-all" work orders should be so once we get that released if you change the WO status for the generic WO, the delay should go away.  Reverting to a prior program version is generally not a good idea because data file structures do change.  If it is a prior patch but the same numbered version (2016.1) then it is OK because by definition data structures do not change within the same numbered version.  Going back to 2015.1 or 2015.2 is not advised.