Answer / coolboy

Hi,

Here we will use joiner for better performance.We will join
the two sources making source table as master source.so
only 100 comparisons will be done.So it will be very faster.

Whereas in static and dynamic we have to look up on the
target which is very large 5m rows.So caching will take
more time.

Answer / arnab

Lookup with No cache will make it faster , personal opinion
though , there are other ways do it also , if you have a
common key between the source and the target and they are
on the same database , it would be easier and faster to do
a join in the source qualifier itself and let the database
handle the query rather than Informatica server

Answer / srinu

My understanding from ur ques--Target havining 5 rows
(Related to Sorce source rows),

Can u Explain (5 m rows Briefly)


srinu.srinuvas@gmail.com

Answer / vijaykumar

Answer 7# is wrong because here we have only 1 source. It is
correct in case of 2 sources.

Answer / jaybrata

Unless you want to join in Database, the only option considering performance is - USE NO CACHE.

BUT, you have to have proper index defined on your target database table, this is crucial as otherwise there will be 100 full table scans on 5 million records.

Static Cache is the worst option as it will always cache 5 million records just to compare 100 records.

Dynamic cache is not an option assuming 100 source records do not contain duplicate.

Informatica side joining is also not good, better to join in DB side instead (To know why and to check the comparison between Infa side and DB side joins, check www.dwbiconcepts.com)

Answer / jaspreet banga

Its better to use connected dynamic non-persistent lookup
transformation, to lookup into the traget and if record
exist , update it else insert the new using unconnected
lookup tranmsformation..

Answer / ajay bhosal

Uncached lookup can give you good performance here but only when your target is properly indexed. Moreover, it's not a good idea to hit the database 100 times and scan huge data volume in the database.
Similar or better performance can be achieved by using Joiner with Sorted Input, but ensure that 100 rows are in master pipeline and the detail pipeline is sorted.
There is no question of using cached lookup.
Answer will be Joiner.

Answer / achoudhr

I wanted to ask, why Static is better than other 3 options.

Answer / srik

5m => 5 million recors.

1) Since target side records are very huge compared to
the source, caching is not preffred. so No caching.

2) Again with no caching we can accomplsh this in 2 ways
a) By Joiner
b) Unconnected lookup
but as unconnected lookup is not in answers is in the
option, Joiner is the answer

Answer / prakash

USE NOCACHE,IT WILL GIVE BETTER PERFORMANCE RATHER THAN
JOINER

Why we use partitioning the session in informatica?

2 Answers  

You have defined the following: - Commit Type = 'Target' - Commit Interval = 10000 - writer buffer block can hold multiple 7,500 rows - you are loading 40,000 records into the target After how many records will the Informatica Server issue commit commands? a)7500, 15000, 22500, 30000, 40000 b)15000, 22500, 30000, 37500, 40000 c)15000, 22500, 30000, 40000 d)15000, 30000, 40000

7 Answers   Deloitte,

What happens if the info. Server doesn't find the session parameter in the parameter file?

1 Answers  

HOW CAN I SEND HALF OF THE RECORDS TO ONE TARGET AND REMAINING TO OTHER TARGET?

6 Answers  

What is the difference between Normal load and Bulk load?

5 Answers  

Do joiner transformation use cache? If so describe?

2 Answers   Patni,

How will u find weather dimension table is big in size of a fact table?

1 Answers  

In update strategy target table or flat file which gives more performance ? why?

7 Answers  

Describe expression transformation?

0 Answers  

From where we can start or use pmcmd?

3 Answers  

explain about session partitions ?

1 Answers  

What is limitations of truncate and load option

1 Answers   Cap Gemini,