Using same tMap component to handle multiple primary key constraints
Hello there,
i have two delimited files.
File-1 : contains records to be inserted in DB (to be processed).
File-2 : contains records that are already inserted in the DB(already processed).
The fields in the table are:
id(PK), name(PK)
I use File-2 as a lookup for File-1. The flow is attached as "Deduplication.jpg".
I use tMap and the configuration is attached as "Mapping.jpg".
The problem is my setup is working like as a composite.
That is i need to check that the id should be unique as well as the name should also be unique.
The setup is working as it checks only if both the (combination of) id and name are unique.
I can accomplish the task if i can use 2 tMap components.
But in future i may have to check 5 to 6 attributes in table to be unique from a set of 20 attributes.
Is there a way so that i can accomplish the task by using only one tMap component???
Please provide me the example....
Can somebody help me?????????
here is a thought... Use the same file to lookup twice. On the first one lookup by the ID, on the second one lookup by NAME. Make the both lookups left outer joins.
