The size of history table is growing unproportionately to number of cases being created/updated. Hence the database is being out of space. The DB size has been incremented allmost 3 times in last 30-45 days.
Activity performed recently:
There were a migration to AWS cloud from on-premise and also pega version were updated from 7.1.5 to 7.1.9.
This growth in history table and ultimately size in the database happening post upgrade. is there any setting that might have been missed in configuration which causing to add much more than needed history information or anything else that can resolve this issue?
thank you in advance for your time for putting effort to suggest a resolution!
Also, according to the support ticket you raised about the growth of pc_History_MGL_FW_eProvisionFW:
These were the suggestions our support team gave you:
1- Look at the data in the table and understand if / why more data is generated compared to earlier. As per Pega DBA creating indexes on the columns used in the where clause of the SQl will definitely help in improving the performance when querying the history table.
2- Requested you to use Purge/Archive option in Design Studio to define work item purge or archive criteria and to schedule it for purging/archiving of old records as required :
3- Requested you to check with DBA if the corresponding SQL query can be improved. Insert query to the history table can be obtained from the PegaRULES-ALERT log.
4- With regards to how to customize or control what goes into the History table, we recommend you to engage Pega Consulting services in order to have someone work with your team.