Answer Posted / sunil

Joiner is faster than lookup. because by default lookup writes order by clause on every column connected to that transformation which decreses the performance..so joiner is faster than lookup..

If anything wrong pls let me know...am looking for job..

Briefly explain your complete project(sales) flow, (ie. from source received from client, transformations, then despatch to end user) what are all the process. Kindly give step by step process.

2325

---

Explain joiner transformation in informatica

1174

---

Explain what is informatica metadata and where is it stored?

1108

---

What are the transformations that cannot be placed between the sort origin and the joiner transformation so that we do not lose the input sort order?

1231

---

What are the performance considerations when working with aggregator transformation?

1209

---

What are the measure objects?

1256

---

5. Consider the following products data which contain duplicate rows. A B C C B D B Q1. Design a mapping to load all unique products in one table and the duplicate rows in another table. The first table should contain the following output A D The second target should contain the following output B B B C C

1959

---

Tell me can we override a native sql query within informatica? Where do we do it? How do we do it?

1115

---

How can we delete duplicate rows from flat files?

1311

---

Write the different tools in the workflow manager?

1119

---

What are multi-group transformations?

1165

---

Is it possible to revert a global repository to local one and why?

1135

---

Give one example for each of conditional aggregation, non-aggregate expression, and nested aggregation?

1320

---

Design a mapping to get the pervious row salary for the current row. If there is no pervious row exists for the current row, then the pervious row salary should be displayed as null.

1345

---

Explain the difference between mapping parameter and mapping variable?

1083

---