Answer / vijay pal

It depends upon the Situation...
In Homo-genous sources(both the sources are RDBMS), Joiner
has good performance
In Hetro-genous sources (like RDBMS & Flat file) look up
would be better.

But If you want RDBMS data in more than one places, better
go for Lookup than Joiner

Hope it have answered you question :)

Answer / etl guru

Give the perfect solution.Every knows what told.

Answer / 78swapnil

All you guys are correct. But there is a major difference between lookup and joiner is, when you join the table we need to join on the basis of a join condition (=) but in case of lookup you can get the data join conditions like (=,!=,<=,>=).

Answer / lokesh.t

lookup is having multiple advantages compare to joiner
transformations :-it will avoid duplicate vlues . by
using first last value in lkp values . with lkp we can n
nnumber of tables. where as in joiner we can join only
two tables

Answer / pawan

R u looking for flat or database file?
Generally sorted joiner more effective on flat files than lookup, because sorted joiner uses merge join and cache less rows. Lookup caches always whole file. If the file is not sorted, it can be comparable. Lookups into DB table can be effective if the DB can return sorted data fast and the amount of data is small, because lookup can create whole cache in memory. If DB responses slowly or big amt of data r processed, lookup cache initialization can be really slow.
Then it can be better use sorted joiner, which throws data to output as reads them on input.

Answer / m.m.basha

performwise both (connected& unconnected) are best
connected lookup :-it is connected to the source
unconnected loockup:- it is not connected to the source

IN A MAPPING WHEN WE USE AGGRIGATER TRANSFORMATION WE WILL USE GROUP BY PORT. IF GROUPBY IS NOT SELECTED BY DEFAULT IT WILL TAKE ONLY THE LAST COLUMN WHY????

3 Answers   IBM,

how to get flatfile containg 10 records half records one target another half another target

2 Answers  

How to compare Source and Target table, without using dynamic lookup?

4 Answers  

my source having the records like ram 3 sam 5 tom 8 and i want to load into target like ram record 3 times,sam record 5 times, tom record 8 times

3 Answers   Satyam,

what is the difference between stop and abort?

3 Answers   TCS,

Is it possible to update the target table with PK?

1 Answers   TCS,

One of the optimizing technique to improve the session performance is push down optimization,by using push down optimization we push as much as transformation logic to source/target database,but this degrades the d/b performance,how to overcome this?

0 Answers   TCS,

Suppose in the next version of Informatica, RTR Xn is excluded. Then how will u route data to different tgts?

2 Answers   Deloitte,

how to convert 101 raja 101 raja sekar reddy 101 sekar----------> 101 reddy

2 Answers  

i have a source with 100 records.i have 2 targets.in the first target i want to load first 50 records & in the second target i want to load next 50(or remaining) records.

3 Answers  

rank() over (partition by opt2.dim_plat_site_id, opt2.dim_site_opt_sid order by case when opt2.dm_market_flg in ('Y', 'U') then 1 else 2 end, lkp.contact_rank) as rank1, case opt2.contact_type when 'Buyer' then row_number() over (partition by opt2.dim_plat_site_id, opt2.dim_site_opt_sid, lkp.contact_rank order by has_name_flg desc, ship_to_flg desc , last_order_dt desc) when 'Decision Maker' then row_number() over (partition by opt2.dim_plat_site_id, opt2.dim_site_opt_sid, lkp.contact_rank order by has_name_flg desc , last_quote_dt desc , mailability_score desc , source_ranking desc) when 'Influencer' then row_number() over (partition by opt2.dim_plat_site_id, opt2.dim_site_opt_sid, lkp.contact_rank order by has_name_flg desc, mailability_score desc, source_ranking desc) when 'Payer' then row_number() over (partition by opt2.dim_plat_site_id, opt2.dim_site_opt_sid, lkp.contact_rank order by has_name_flg desc, mailability_score desc, source_ranking desc) --elu 05/28/2013 else row_number() over (partition by opt2.dim_plat_site_id, opt2.dim_site_opt_sid, lkp.contact_rank order by has_name_flg desc, mailability_score desc, source_ranking desc) end rank2 row_number() over (partition by opt3.dim_plat_site_id, opt3.dim_site_opt_sid order by rank1,rank2) as "rank", case when "rank"<= opt3.maximum_value then 'Y' else 'N' end as include_flg

0 Answers  

1:when we develop a project what are the performance issue will raise?? KPIT 2:if a table have INDEX and CONSTRAINT why it raise the performance issue bcoz when we drop the index and disable the constraint it performed better??KPIT 3:what are unix commands frequently used in informatica??

1 Answers   KPIT,