Doing a lot of testing for potential cutover using the DMT to upload date into E10. What we’re experiencing is we can barely upload job data (and I mean Job data ONLY) in a weekend. Does ANYONE have any ideas on how to get more throughput from the DMT?
SQL tuning (We’ve had Epicor pass us through the stress test).
We’re getting like 22-60 rpm in uploading Job Operations and Job Materials into E10. At ideas? We’re looking at something like 12 hours for just Job Operations and almost 24 hours for Job Materials. Please advise.
Have you split your files and run multiples at the same time? In the same dmt instance you can open more than on of the same job operation or job material windows. Then you usually can run between 6 and 10 at a time and each will get about the same speed.
pretty much 1 instance.
I split the files as best I can - unfortunately when I split the file using the file splitter, I get mixed results and (usually) wind up with a ton of bogus errors - and still running slow. I have split the file by the jobs according to the plant they are being run in (and the bogus errors go away).
When I do split the file using the file splitter, I get a ton of errors - mostly bogus. I have found that they run clean(er) when I break up the files according to the manufacturing plant they are associated with. Still even doing that, the majority of records (about 70-80% - maybe higher) are associated with a single plant.
Regardless of how many sessions / files I split this particular import to, it ALWAYS runs slow…