Our pc_history_work table is taking aroun 52% of total DB Space
Hi Everyone
We received an alert about our Staging DB being around 76% utilization when checking into PDC, we found that pc_history_work is taking around 52% of the total available space.
We would like to purge this table, to keep maybe the last year's worth of records, but we don't want to mess anything up in the process.
Can we do this or does this table hold information that, if deleted, could break the environment?
Thanks,
Updated: 29 Nov 2023 15:05 EST
Ordina
NL
@Junicavi Truncating or purging history tables should normally be safe. Lots of history tables for implementation classes are mapped to something else than pc_history_work usually, for those it would depend on your data retention policy. I'm not enitrely sure about the OOTB tables that are mapped to pc_history_work but given the purpose that history tables have in general, it should not be breaking anything.
The old purge and archive wizard is no longer officially supported as per Pega documentation, but take a look at the options in https://docs-previous.pega.com/system-administration/86/purging-and-archiving-old-work-items.
If for some reason the options do not support your requirements in the future, take a look at https://support.pega.com/discussion/when-we-should-use-rdb-methods-over-obj-methods for reference. For example, we had a fast growing history table due to an infinite loop in a flow and needed to clean up fast, so we ran a job that used an RDB-method instead of an Obj-Delete. Wowing performance.
Pegasystems Inc.
CA
@Junicavi Check if there are too many entries of information written in the Audit logs for each case. This will help to prevent this issue further after you truncate or purge the history tables.