Database Purge

[askulte (Andris Skulte)]

https://www.epiusers.help/search?q=database%20purge%20order%3Alatest

Archiving Data

@rholndoner - We run database purge & summarize annually to keep the size down (Transactions, Journal Details, and Change Logs), with a 3 year lookback. Before the purge, we copy the purged tables into a separate SQL database, so it’s available offline just in case… We’re not cloud, but I’d assume you could do the same with a gigantic BAQ export. Be careful on the Journal Details purge. Epicor will remove the GL records of open invoices too (an issue if you have terms with a long duration). You…

Do you prune Change Logs? Ice.ChgLog

I’ve heard warnings many times before about how Change Logs can hinder database performance. This led me to check on the size of our Change Log table. One can do this with the following SQL query: sp_spaceused ‘Ice.ChgLog’ It occurred to me this morning that nearly all use cases for how we use Change Logs is for something recent, for example we want to know who changed a date on an open Sales Order and have a daily BAQ report that tells us. Chances are though, once 6 months have passed we’ll…

Change Log Efficiency - "New" rule: BE CAREFUL!

We were down this same path, with lots of change logs going way back. Finally decided to skinny down the # of fields logged and only keep the most recent 2 years. We purged the rest with the ‘Database Purge & Summarize’ process, and now run it monthly. There’s no filter on it besides the cut-off date, but it will delete a ton of old garbage. Make sure to check ‘Change Log’ and not something else by accident! [image] Careful if you do use the purge and summarize process for the Journal Details…