from Source 100 rows are coming, on target there are 5 m
rows which options is better to match data
1. Joiner
2 No cache
3. Static
4. Dynamic
Answers were Sorted based on User's Feedback
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.
| Is This Answer Correct ? | 28 Yes | 3 No |
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
| Is This Answer Correct ? | 6 Yes | 3 No |
Answer / vijaykumar
Answer 7# is wrong because here we have only 1 source. It is
correct in case of 2 sources.
| Is This Answer Correct ? | 2 Yes | 0 No |
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)
| Is This Answer Correct ? | 1 Yes | 0 No |
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..
| Is This Answer Correct ? | 1 Yes | 0 No |
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.
| Is This Answer Correct ? | 1 Yes | 0 No |
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
| Is This Answer Correct ? | 2 Yes | 2 No |
Answer / prakash
USE NOCACHE,IT WILL GIVE BETTER PERFORMANCE RATHER THAN
JOINER
| Is This Answer Correct ? | 1 Yes | 1 No |
While importing the relational source definition from the database, what are the metadata of source that will be imported?
In pmcmd command we need to type -p:password. Will it be visible to others who is having access to this file ?
What are two types of processes that informatica runs the session?
Define informatica repository?
What the difference is between a database, a data warehouse and a data mart?
What is dimensional table?
WAT IS THE MEANING OF UPGRADTION OF REPOSITORY?
In What Situations we can use MappingParameters ,Mapping Variables AND Session Parameters in REAL TIME.
Can anyone please distinguish what is Inner join and Outer join
What is the default join that source qualifier provides?
I have one source table and three target tables. When the session runs for the first time involving the mapping,i want that the loading should take place in 1st Target table only. The 2nd time the same session runs the loading should take place in 2nd Target only only and similarly when the session runs for the 3rd time loading should take place in Third only. And again when the session runs for the 4th time loading should take place in 1st Target table.
what is the method of error handling when session is running?