Delete Mass Records from archive table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello everyone,
I need a help in deleting 4 million records in a archive table which is ar_sys_email, what is best and safe way to delete these mass records.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hey @deekshithkd
I'd recommend making a Destroy rule that aligns with your Archive rules. This can be defined that X amount of time after a record is archived, it should be permanently deleted.
Once you've set this up, it will start running every hour and will slowly but surely get rid of the backlog and then continue deleting newer archived records that meet the threshold 🙂
If this hasn't helped, reply and let me know and we can keep working the problem!
If this has helped, please mark the answer as correct so others with a similar problem can find the answer 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @deekshithkd
For this volume around 4 million records, avoid deleting everything at once. The safest approach is to delete the records in batches using Table Cleaner, Archive Cleanup, or a background script that processes a limited number of records at a time like 10k–50k per batch. Also, schedule the cleanup during off-peak hours and test it in a non-production instance first to minimize performance impact.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello @deekshithkd
For this volume around 4 million records, avoid deleting everything at once.
The safest approach is to delete the records in batches using Table Cleaner, Archive Cleanup, or a background script that processes a limited number of records at a time like 10k–50k per batch. Also schedule the cleanup during off-peak hours and test it in a non-production instance first to minimize performance impact.