there should be some way to limit the lookup data that is written to a hashed file.
e.g.
i extract 100 000 rows from a source (lets assume a subset of the customer base) and need to do a lookup on the latest order from a table in a different system with 10 000 000 rows (lets assume its the orders summary table). It would be beneficial to pass the list of account numbers into the job that creates the hashed file. This means that I only load 100 000 rows into the lookup, not records for each customer!
limit the lookup data in a hashed file
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Limit in the SQL that extracts data to load in the hashed file.
Code: Select all
SELECT ID, othercols FROM sourcetable T1 WHERE EFF_DATE = (SELECT MAX(EFF_DATE) FROM sourcetable T2 WHERE T1.ID = T2.ID)
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.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: