Question
HAP
US
Last activity: 13 Nov 2015 11:55 EST
What is the recommended size of a table to be a good case of Purge & Archive?
What is the recommended size of a table to be a good case of Purge & Archive?
Our application has been running for around three years, there are over 5 million records in our work table. Is there any specific recommendation for Purging & Archiving?
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
GovCIO
US
Even I also have the same doubt in my mind to ask. Good that you pointed our in right time, Manish. Let's wait from the experts to respond on this.
Pegasystems Inc.
US
Purging and Archiving requirements should be discussed with business and it will be govern by your audit and compliance requirements. having 5 millions records is not an issue, if you see legacy claims applications they will have tons of millions of records and database will be able to support that very well.
There are few clients who have moved some data to archival DB/tables so the business can see limited data in review harness.
HAP
US
Hi Ritesh,
Does this mean that we can view the archived & purged cases in review harness?
Pegasystems Inc.
US
OOTB Pega doesn't do that but we need to build something. We have developed some solution for AIG, BOA and ING Europe. Please work with someone in PS team to develop the solution at your end.
Pegasystems
US
I'm not an expert, but I can offer some general guidance:
It's a balance of performance and disk space.
I assume that most of your millions of work objects are inactive ones and only a small percentage of them are currently being worked.
If you've got plenty of disk space for those millions of records, and they are sufficiently backed up to protect you in case you lose them, and your particular db is exhibiting good performance even though there are millions of unused work objects, then no purge/archive is needed.
However, if those millions are slowing down the performance, then that would be one reason to consider purge/archive.
Or, if performance is ok but your disk space is getting low, again, consider purge/archive.
Another consideration is whether you need to search those millions for reference. If you've used the Pega indexing feature, I don't know whether the index is usable for search even though the underlying work objects have been purged and archived. They definitely would no longer be searchable if you rebuilt the index after purge/archive.
/Eric
HAP
US
Thanks Eric and Ritesh for sharing your views
Pegasystems Inc.
US
If you do set this up, you have the option of running the process from scripts. I've seen it mentioned that Purge/Archive scheduling with Pega Agent is not recommended for any "backlog" over 100,000 records - especially if the work cases have children who might have children. Then, once you're caught up, you can either use the scripts on a schedule or configure the Purge/Archive in Pega as "maintenance" on a manageable number of work cases weekly or how ever often you have it run.
Are all the work objects in the same work pool (single table)?
HAP
US
Thanks for your comments Paul. To answer your question - No, we have four different applications, all of them have their own workpool.