Then we get the phone-call, it is urgent, the team has underestimated the time it will take to migrate the data and project timelines are in danger, or the excess ERP data is raising red-flags for the auditors. 

With our Datawaire Data Management Service you can avoid that panicked phone call, our team ensures that JD Edwards data does not grow out of control and is optimised to ensure optimal database and application performance. 

Thanks to our over twenty-years working with JD Edwards clients we know some of the key issues to look out for. There is a non-exhaustive list below of some of the issues we encounter most often: 

1. Supersized tables
   When we run our JD Edwards Database Health Check we can see the size of each table as a percentage of the entire database. When you see tables taking up to 25%+ of the total database then it it time to start thinking about archiving.
   
   
2. Beware of Temporary Copies of Data Files
   We have seen our fair share of F0911_SAV. There was probably a good reason to take a copy of the table(s) at the time but sometimes we forget to come back and remove these “temp” files.
   
   
3. F0911 Batch Types
   F0911 tends to be one of the largest tables in many databases. To archive effectively you need to examine the batch types contained in the F0911 and target those files with the highest number of entries. Each batch type will often require different Modules to remove the records.
   
   
4. Work Order Selections 
   Every site will potentially have different Work Order document types and Work Order status codes. Each site will need to be involved in the decision of what Work Orders and status codes should be included in archiving.
   
   
5. Custom Tables 
   Custom tables defined by each site will not automatically be included in the list of tables to be targeted. However once identified we can flag those that we wish to target for archiving as “Custom” which will factor them into the archiving stats. Custom tables can be targeted by either appending logic to existing modules or creating new modules.

Don't Forget You'll Need More Space than you Think
To Archive 100Gb of data requires 100Gb of empty disk space to be available. Even when we purge the archived data from production the space created by the deleted records is not returned as available until a re-org of table spaces is run. So keep in mind that the amount of disk that will be archived is also the amount of available disk space that will be required in the archive schema.