Hello all,
In a Datastage Enterprise Edition job, is it possible to refresh a lookup to reflect inserts done to the lookup table within the same job?
My job writes records to a table X, It is capable of insert new records, insert new versions and update old versions of existing records. The lookup to identify existing records and new versions is done to the same table X. The problem arises because the input data may have several versions of the same record inside.
Thank you in advance
How to refresh a lookup table after every iteration
Moderators: chulett, rschirm, roy
No, the only way to do this is to use sparse lookups and no buffering of output.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
That's entirely a matter of how you design, and (I believe) what Arnd meant by "no buffering of output". YOU control the number of rows per transaction - for auto-commit set it to 1.Vardhini wrote:Will the sparce lookup auto commit records:?:
That depends. Define "performance" in an ETL context.Vardhini also wrote:and also using a sparce lookups will decrease the performance of the job.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.