I am interested on the horror stories of the "PURGE" function. Please do share some out.

For archiving, I noticed a client requested me to create a duplicate folder of the currently running production folder yearly.

Then they maintain from their end to clear out non-essential data for the new year manually and slowly archiving the old production folder and removing from X3 once done to actual archive drive.

For purging, if it is just the logs, I did a clear table from table screen.

I did managed to kill a database because of an extreme purge run (X3 logs size was x3 of X3 masterdata) which the SQL Server log file (it was set on Recovery Model: FULL) was not built to account for such the edge case without prior heads-up.

Masterdata purge I have no experience so I am interested in how everyone did for those along with archiving activities.

Hi Martin,

If you have a client on V11 then upgrade to V12 before you start the archiving process. I do not believe you can migrate archive folders at V11.

Purging is not a problem and we use it at every version for clearing down trace files and batch requests as well as ALISTER and other supervisor tables.

I would not recommend using CLEAR on a table record. Trace logs are there for a reason and it is always worth holding a few months records, just in case.

The following document is available from Sage UK support team (Mike Shaw)

Sage X3 – Housekeeping suggestions X3 Version 12

The standard archive processes are very good and include connections to other relevant tables that are not always listed.

For example:

Purchase Orders has about 6 tables mentioned in the archive record POH but it will also clear down the relevant CPTANALIN and GACCDUDATE records if required.

It also checks to ensure that there are no outstanding unvalidated invoives against a PO that is showing already as closed and fully invoiced.

Set recurring tasks to run your archiving and purging and it will all happen overnight. Each batch request can give you a log showing what was archived or purged and what could not be and the reason for that.

Hope that helps

> If you have a client on V11 then upgrade to V12 before you start the archiving process. I do not believe you can migrate archive folders at V11.

https://www.sagecity.com/gb/sage-x3/b/sage-x3-uk-support-insights/posts/time-to-tidy-up

But yes, I have just read but never confirm personally yet.

Currently labbing this out.

Doing a test update patch from v11p20 to v11p21.

Will do a validation run tonight to confirm access to HSEED tomorrow.

Migrate first and then create the archive folder. Do not create the archive folder and try to migrate it.

From X3, VALDOS on HSEED worked.

Left is SEED, right is HSEED.

Now to see what happened after a folder migration from v11 to v12 using this kb (106199) as a reference: support.na.sage.com/.../viewdocument.do

Well it does took a long while but finally migrated over.

There was a minor hiccups on HSEED side so I restarted the process in Sequencing Monitor.

Looking fine.

Also, from online help for reference on archiving and purge process: online-help.sageerpx3.com/.../archivepurge and online-help.sageerpx3.com/.../APARHIS.htm

Another one but a technical overview reference: www.sagecity.com/.../performance-tuning-your-sage-x3-system-x3-specific-considerations