on 12-17-2012 4:10 PM
I am looking at an existing job in my project, where they used "map_operation" transform object for each criteria, is it not possible to track all Inserts, Updates and deletes in one shot using one Map_Operation transform object?
This is how it is within a job right after Tbl_Comparison Object:
one for to track Update
(Normal-discard, update-normal, insert-discard, delete- discard)
One for to track deleted rows
(Normal-Discard, update-Discard, insert-discard, delete- Normal)
one for to track newly inserted rows.
(Normal-discard, update-Discard, insert-Normal, delete- discard)
Thanks a lot for the helpful info.
I forgot to answer your questions - yes it is possible to process all operation codes through one map operation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is common to use multiple map operation transforms where you need to apply separate logic for the various operations. For example, you might want to process a delete as a delete and an insert into an audit table,but leave inserts and updates as they are. However, in some cases people mis-use it when applying slowly changing dimension logic.
Is there different logic after each map operation?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.