I am noticing that if changes are being made to the destination table in a data integration job (i.e. adding, renaming, or removing fields) it is causing significant performance issues. This seems to happen even though the fields are being updated in the data integration job to reflect the changes (and in some cases the fields aren’t even being used in the data integration job). It seems that the old field references are still hanging around in the XML. It appears the only way around this is to recreate the data integration job or modify the XML to remove the old field references. Is this expected behavior?
Developer forum
Changes in Destination Table Results in Slow Performance in Data Integration Job
Byron Head
Replies
Dmitriy Benyuk
Posted on 22/03/2024 16:30:03
Hi Byron,
usually that should not happen. What are your source and destination providers used in the job? What is the job xml file size?
You can try to click on the button "Check tables schema" to remove the not used tables and fields:
BR, Dmitrij
You must be logged in to post in the forum