What is a diff between joiner and lookup transformation
Answers were Sorted based on User's Feedback
Answer / amit
joiner is active transformation & lookup is passive
transformation
Is This Answer Correct ? | 99 Yes | 41 No |
Answer / chandra
Joiner will join the two different data sources based on a
join condition ,and pass only the rows which satisfy that
condition.discards the remaining rows.
Joiner transformation supports 4 types of joins at
Informatica level
Normal
Master Outer
Detail Outer
Full Outer
LookUp Transformation
Lookup transformation basically for Reference,based on the
lookup condition.when u want some data based on target
data ,will take lookup on that particular table and
retrieve the corresponding fields from that table.
we can override the lookup transformation using the SQL
query.
Is This Answer Correct ? | 72 Yes | 19 No |
Answer / gopal
In joiner we can join two heterogeneous sources for entire
records based on a condition.
But in look up only the first value or last value of the
records will be passed if more records matched with that
condition. So only one value will be returned to the
transformation.
EX:
in source : No Name
1 -
Look up table: No Name
1 A
1 B
1 C
Now we can return only A or C in look up.
If we need entire values we must go for joiner. Take that
look up table as source and use joiner. No alternative
solution.
Is This Answer Correct ? | 66 Yes | 24 No |
Answer / jayash
joiner transformation does not match for null values where
as lookup transformation matches for null values
joiner transformation supports only equality operator in
condition of join where as lookup transformation can support
<=,>=,=,!= in the lookup condition
Is This Answer Correct ? | 47 Yes | 8 No |
Answer / sweta kedia
. I) Joiner is active transformation & lookup is passive
transformation.
II) Joiner operates on sources where as lookup operates
source as well
as target.
III)Joiner doesnt support nonequi joins whereas lookup
supports nonequi join
i.e. joiner transformation supports only equality operator
in condition of join where as lookup transformation can
support<=,>=,=,!= in the lookup condition.
IV) Lookup uses dynamic and static cache where as a joiner
doesn’t.
V) Joiner transformation does not match for null values
whereas lookup transformation matches for null values.
VI) Joiner will do left outer,right outer,normal,full outer
types of joins whereas lookup will do only left outer join.
Is This Answer Correct ? | 34 Yes | 3 No |
Answer / mythili
Hi everybody,
Joiner is active transformation whereas lookup is passive
transformation.
Joiner returns only matching records whereas lookup
returns null if there is no match.
In join condition we can give only '=' operator but in
lookup condition !=,>=,<= are all possible.
Joiner will do left outer,right outer,normal,full outer
type of joins whereas lookup will do only left outer join.
Is This Answer Correct ? | 31 Yes | 9 No |
Answer / bsgsr
hi, everyone.
lookup is passive whereas is joiner is active.
look up supports non equi joins ilso whereas joiner
supports only equi joins.
lookup joins on either on first value or last value.
lookup uses dynamic and static cache where as a joiner
doesnt
reach me on bsrinivas1213@gmail.com
Is This Answer Correct ? | 22 Yes | 11 No |
Answer / eswar
Use the Joiner transformation to join source data from two
related heterogeneous sources residing in different
locations or file systems. You can also join data from the
same source. The Joiner transformation joins sources
with at least one matching column. The Joiner
transformation uses a condition that matches one or more
pairs of columns between the two sources.
Use a Lookup transformation in a mapping to look up data in
a flat file, relational table, view, or synonym.The
Integration Service queries the lookup source based on the
lookup ports in the transformation and a lookup condition.
The Lookup transformation returns the result of the lookup
to the target or another transformation.
The Joiner transformation supports only equi joins and
Lookup Transformation supports equi and non-equi joins
The Joiner transformation lieterally joins two columns
whereas Lookup transformation return a column based on the
condition, but it will not joint two columns.
Is This Answer Correct ? | 13 Yes | 3 No |
Answer / swathi naik
I) Joiner is active transformation & lookup is passive
transformation.
II) Joiner operates on sources where as lookup operates
source as well
as target.
III)Joiner doesnt support nonequi joins whereas lookup
supports nonequi join
i.e. joiner transformation supports only equality operator
in condition of join where as lookup transformation can
support<=,>=,=,!= in the lookup condition.
IV) Lookup uses dynamic and static cache where as a joiner
doesn’t.
V) Joiner transformation does not match for null values
whereas lookup transformation matches for null values.
VI) Joiner will do left outer,right outer,normal,full outer
types of joins whereas lookup will do only left outer join.
Is This Answer Correct ? | 7 Yes | 2 No |
if i have 10 records in my source,if we use router t/r and given the condition as i>2,i=5 and i<2in the different groups what is the o/p in the target
what is the logic will you implement to load data into a fact table from n dimension tables?
If I have set the property Treat Source Rows as Insert and for the target properties I have checked the boxes Update as Update, what will happen to incoming rows? What exactly is the use of these check boxes and in which scenarios we use them. Also what is the sequence in which informatica understands these properties.Does it takes whatever is defined in treat source rows as property or it is in any other way. Please explain.
What's the layout of parameter file (what does a parameter file contain?)?
why dimenstion tables are denormalized in nature ?
Hi Friends, I want lo truncate my records from target before loading current month data,but i dont have permission to truncate with truncate option if u know any other way please give your valuable input for this. Thanks Abhishek
Explain lookup transformation source types in informatica
when we use dynamic lookup,if condition matches what will be the o/p?
SRC1 -> EXP -> AGGR -> TGT SRC2 -> EXP -> Above is a maaping with two pipeline connected to the taret TGT. Design wise is this design is correct or not ?
Implementation methodology
How many mapplets u have created? and what is the logic used
How to generate a single mapping for both the historical and incremental load.