Lookup design
Posted: Sat Feb 07, 2015 11:32 am
All,
Have a question in lookup design. we have a complex jobs which loads Table A everyday. Now, i want to make sure next day whatever record is there in Table A should not load. Used look up stage before loading into Table A.
--------------- Table A
------------------ |
Source-- Lookup- Table A.
Kind of confused in Lookup properties. In server jobs we use not(not found) in link variables in transformer. Seems like this is not available in Parallel.
Basically, suppose if 200 records comes from Source and it has look up based n employeeid, (let 1 record is already in Table A). it 199 record will load and 1 record will drop..
Any thoughts. Thanks.
Have a question in lookup design. we have a complex jobs which loads Table A everyday. Now, i want to make sure next day whatever record is there in Table A should not load. Used look up stage before loading into Table A.
--------------- Table A
------------------ |
Source-- Lookup- Table A.
Kind of confused in Lookup properties. In server jobs we use not(not found) in link variables in transformer. Seems like this is not available in Parallel.
Basically, suppose if 200 records comes from Source and it has look up based n employeeid, (let 1 record is already in Table A). it 199 record will load and 1 record will drop..
Any thoughts. Thanks.