Mapping Editor vs. Data Movement Model
we are in process of mapping source to target tables (and attributes of course).
I'm asking myselft, if we really should use the DMM or maybe the simeple mapping editor will do the job ...
My biggest concern is, we have sometimes "logic" inbetween, like for example:
1. TargetTable1.Column1 is a concatenation of SourceTable1.Column1, SourceTable2.Column2, Sequence.NEXTVAL
2. TargetTable1.Column2 is populated from a lookup table LookupTable1.Column2 based on SourceTable1.Column2 (it's a conversion INT -> CHAR)
3. There are some calculations for some INT attributes, like -,+,/ and * operations
Can I utilize the mapping editor to model all of this, or shall we really stict to DMM.
DMM is quite complitated and close to the logic of Replication Server. For example, I was trying to calculate a new attribute, and was forced to pick a data type for this attribute... but there are noly typical Replication Server data types available....
So back to my question: is there a rule, defining how far can I go using the simple Mapping Editor?
I found this post: Impact and Lineage Analysis setup for a dwh
But again ... this would indicate, we have to switch to DMM.