Given that the purge process is time-consuming and requires extensive monitoring, why can’t we use direct database operations to remove old data instead?
Hi There,
Using direct database operations to delete case data in Pega is risky because you have to manually find all the related tables. If you miss any, leftover data can cause issues and may break compliance rules.
Pega’s purge process is designed to safely remove all related data. It automatically finds and deletes everything in the right order, keeping the system clean and avoiding problems like broken links or errors.
Benefits of using the purge process:
-
Keeps Data Consistent: Deletes related data in the right order.
-
Runs Important Logic: Triggers things like audit logs, archiving, or notifications.
-
Better for Performance: Deletes data in batches to avoid slowing down the system.
-
Follows Rules: Supports data retention and compliance requirements.
In short, Pega’s purge process is a safer, smarter, and more reliable way to clean up old case data than using direct SQL deletes.