Advice on reducing size of database tables
Our development database size currently seems to be exceeding 20GB and customer have asked us to provide some inputs on expected database size/capacity to control backups/disk space etc..
Out of the 20 GB,
13-14 GB seems to be Rules data
2-3 GB is application data
3-5 GB seems to be other system data tables like pr_perf_stats, pr_sys_statusdetail
I have attached an excel showing top system tables occupying space in our database
Platform – 7.1.8 with Customer Services 7.1.3
Is there a guidance document available somewhere which I can refer to understand the expected
Our development database size currently seems to be exceeding 20GB and customer have asked us to provide some inputs on expected database size/capacity to control backups/disk space etc..
Out of the 20 GB,
13-14 GB seems to be Rules data
2-3 GB is application data
3-5 GB seems to be other system data tables like pr_perf_stats, pr_sys_statusdetail
I have attached an excel showing top system tables occupying space in our database
Platform – 7.1.8 with Customer Services 7.1.3
Is there a guidance document available somewhere which I can refer to understand the expected
- Rules/system data tables growth w.r.t application data
- What can be turned off w/o impacting application to reduce size of rules/system data tables
- Some other literate which can aid understanding and knowledge in this area
***Updated by Moderator: Marissa. Removed user added Ask the Expert and FAQ tags. Apologies for confusion, shouldn't have been an end-user option***
Pegasystems Inc.
AU
By default there are some agents that does the house keeping of the cache tables and some of the system tables. You need to ensure that these agents are up and running and also appropriate retention period is configured for them.
Other than the above, housekeeping of the application data or work objects tables should be done by configuring the Purge & Archiving process. Please note that you can tidy up the rules tables by deleting the unwanted rules/rulesets, skimming the rulesets.
Pegasystems Inc.
AU
Below are some of the tables that has large data at your end.
PR_index_reference:- Stores instances of the Index-Reference class, which maintains references to rules used within other rules.
Spr_sys_updatescache:- System pulse refers this table. The tables stores instances of the System-Updates-Cache class (rule updates to be distributed to other nodes). Contains one row for each rules change implemented since the most recent pulse. This table is scanned when rules are updated and added to the cache, and is emptied when cache processing completes. Check the frequency of system pulse.
Pr_perf_stats :- Stores instances of the Log-Usage class, used in analysing system performance. Again this table data can be controled by configuring the retention period.
Pegasystems Inc.
IN
Hi Krishna
Thanks for your replies. Did not reply earlier as I wasn't aware of your replies as no automatic notification was sent to me by PDN.
I can also see from the excel list size of the tables which are big however what I am looking for is definitive details of which agents and what configuration (retention etc.) I can change to reduce the size. Do we know which specific configuration I can change to reduce the sizes for each of the tables?
Thanks
Pegasystems Inc.
IN
Hi
Can anyone else in the community reflect on how best to control size of database tables (mainly the ones which are shipped as part of Customer Services and Pega platform)?
Many thanks
Salil
Pegasystems Inc.
IN
Hi Salil,
I would like to invite you to ask your question to our Expert on Pega CS. Click the below link to add a reply asking your question. You could add in the URL to this post to provide context.
Ask the Expert - Pega Customer Service with Goutham Parcha
Regards,
Lochan | Community Moderator | Pegasystems Inc.