We'll probably generate over 1.25 million workitems a year in the database.
Would like to know how your system degrades over time and the strategy for archiving data beyond 1 year (or on a per process basis).
Anyone has over 1 million workitems in the database?
+13
+11- Nintex Employee
Hi Peter,
1.25 million workitems should be fine. Surely this number of items will not be active at the same time so the impact on the K2 transaction database should be minimal. I have seen some timeout errors starting to occur when individual users has 15,000+ worklist items active. If this is the case, you will need to seriously re-think you process design because no one will be able to get through 15,000+ items in a year. Some of my clients ran into this problem and developed a thick client worklist application accessing worklist items through the K2ROM. Some of them have been running for over a year now without any problems.
On the reporting side, you may run into timeout errors due to large volumes of data but this is where the K2Archiving utility comes in. This utility will allow you to move data from the K2Log database to an archiving database. Currently, this utility only supports date-range archiving and not process specific archiving.
HTH,
Ockert
1.25 million workitems should be fine. Surely this number of items will not be active at the same time so the impact on the K2 transaction database should be minimal. I have seen some timeout errors starting to occur when individual users has 15,000+ worklist items active. If this is the case, you will need to seriously re-think you process design because no one will be able to get through 15,000+ items in a year. Some of my clients ran into this problem and developed a thick client worklist application accessing worklist items through the K2ROM. Some of them have been running for over a year now without any problems.
On the reporting side, you may run into timeout errors due to large volumes of data but this is where the K2Archiving utility comes in. This utility will allow you to move data from the K2Log database to an archiving database. Currently, this utility only supports date-range archiving and not process specific archiving.
HTH,
Ockert
+13Active items should be relatively small (no more than 10,000).
Individual user's active workitem would be under 100.
Individual user's active workitem would be under 100.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.