If we use only lookup transformation in a mapping ie,
SourceQualifier-->Lookup --> Target. , here datas are taking
very long time to load in target., so what are steps to
improve the performance in that mapping???????
- 2 Answers
- 5544 Views
- I also Faced
- E-Mail Answers
Answer Posted / hari
use order by clause in source qualifier.
Remove un necessary ports in that lookup.
try to restrict lookup cache based on the source data.
create order by clause in lookup override using the lookup
condition columns.
If lookup and source are in same database try to join in
source qualifier.
Drop the indiex on the target table before loading the data.
Check index on source table,
Check source table look tables are analysed properly or not.
| Is This Answer Correct ? | 7 Yes | 0 No |
Post New Answer View All Answers
What are the different versions of informatica?
What is mapping debugger?
TELL ME ONE COMPLEX MAPPING IN UR PROJECT? chandumba2005@gmai.com
what are the different types of transformation available in informatica. And what are the mostly used ones among them?
How to load last n records of file into target table - informatica
Differentiate between joiner and lookup transformation?
What is domain and gateway node?
Explain scd type 3 through mapping.
How we can create indexes after completing the loan process?
Explain the aggregator transformation?
What is intricate mapping?
how tokens will generate?
Why is sorter an active transformation?
suppose in my source flatfile i have 10000 records in that some of master table records missed table records missed then what will u do
how can we find the bottle neck in SQL Query in SOURCE QUALIFIER, and how can we tune it..?
