Multiple lookups against same dataset
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 28
- Joined: Thu Sep 29, 2005 1:50 pm
Multiple lookups against same dataset
I need to do multiple lookups for different columns in the source against the same dataset. I cannot use the Range lookup since the values are not necessarily in a certain range.
Do I have to create multiple datasets for each lookup? Or, are there any better options that I can avoid creating multiple datasets?
Thanks.
Do I have to create multiple datasets for each lookup? Or, are there any better options that I can avoid creating multiple datasets?
Thanks.
-
- Premium Member
- Posts: 892
- Joined: Thu Oct 16, 2003 5:18 am
-
- Participant
- Posts: 28
- Joined: Thu Sep 29, 2005 1:50 pm
-
- Premium Member
- Posts: 892
- Joined: Thu Oct 16, 2003 5:18 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
One data set will suffice. Each reference input to your Lookup stage creates a separate virtual Data Set into which the reference data are read and build an index on the identified key (the LUT_CreateOp operator). So you do actually have separate data sets at run time - you don't have to design this feature.
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.
Use a Transformer in between the Lookup stage and dataset stagespeedsterrules wrote: Yes, that is certainly an option but then I am just replacing creating multiple datasets with as many lookup stages. Do you think there is some other options to avoid this? Thanks.
You will get multiple copies of the data or else even you can just map the particular dataset column to multiple columns via transformer and achieve this.
Please post more info (if there is any) about the design which may help our experts to suggest better.
Accept that some days you're the pigeon and some days you're the statue.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
That strikes me as overkill. You can have as many connections to the same Data Set as you require. Ultimately (with either approach) you get N virtual Data Sets for N reference inputs. I don't think the Transformer stage is going to give you anything. If you want to drop columns differently, use Copy stages on each of the reference inputs to the Lookup stage - a far lower cost than Transformer.
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.
Ray,ray.wurlod wrote:That strikes me as overkill. You can have as many connections to the same Data Set as you require. Ultimately (with either approach) you get N virtual Data Sets for N reference inputs. I don't thin ...
I agree - creating many connections from transformer to Lookup stage is nothing but creating N virtual Data Sets.
But, in the transformer he can have the lookup key column mapped into few new columns which can be used in the lookup stage to map with different columns in the source (I believe this not like creating N virtual Data Sets)
Correct me if I am wrong. Thanks in advance
Accept that some days you're the pigeon and some days you're the statue.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: