This content has been marked as final. Show 4 replies
This is dependent on too many factors to give a meaningful answer.1 person found this helpful
Which EIM table are you using?
Which base tables are involved?
How many columns will be loaded?
10,000 records for an "average" EIM job doesn't sound like a lot.
But it also depends on your hardware.
You can also specify multiple batches in the IFB file.
If the last batches are empty, it won't matter.
You can also try to control it through SQL.
Just check the status of the records.
The table EIM table we are using has no direct relationship with the party tables and that’s the good thing as the insert statement deals on 3 columns only and very simple. We setup batch range for this to specify how many records as batch size.
Do you think in less than 10mins the EIM job assume to be completely executed by then? We worry on the potential huge records of 10k but as you say, it does not sound like a lot. So, I presume in 10mins this job will be completed given no error at all? could you confirm?
Though, we can confirm this until it’s live deployment, but I’m anticipating as early as now the probable things to happen based on your project experiences.
Looking forward for the prompt response and again thank you very much.
With the current information it sounds it should be no problem.1 person found this helpful
You do need to make sure that the indexes and statistics are up to date (ask your DBA).
Can't you test this in DEV, TEST oR UAT environment?
We tested it however only small amount of data, not 10k records. But we have decided to have at least 5 minutes gap and we will monitor the performance during the live deployment. Should anything goes wrong then we will do corrective actions. Thank you by the way for your responses, it help a lot. Truly appreciated. Thanks again