Answer / ysindhureddy77@gmail.com

1. SQL Override is to limit the number of incoming rows entering the mapping pipeline
Lookup Override is to limit the number of lookup rows to avoid the whole table scan by saving the lookup time & cache it uses.

2. Lookup Override uses "Order By" clause by default
SQL Override doesn't uses it & should provide in our query if we require it.

3. SQL Override can provide any kind of join by writing the query
Lookup Override provides only Non-Equi joins

4. Lookup Override gives only one record even if it finds multiple records for a single condition
SQL Override doesn’t do that.

In Datastage, we have row generator stage to generate dummy row. Is there any such transformation in Informatica. Thanks in advance, Kumar

1 Answers  

---

What are the tuning techniques you applied during your last project

0 Answers  

---

Have you worked with/created Parameter file

0 Answers  

---

i have two sources both is oracle database . one is coming from USA database and another one is coming from U.k database .i am using source qualifier transformation to join this.as that time in session level source properties which path i need to give to retrieve that data. thanks bala 09619894486

2 Answers   Accenture,

---

What are the limitations of joiner transformation?

0 Answers   Informatica,

---

How can we use mapping variables in informatica? Where do we use them?

0 Answers  

---

what are the perameter and variable?

3 Answers   IBM,

---

Can we use the mapping parameters or variables created in one mapping into another mapping?

1 Answers   Informatica,

---

In a sequential batch can u run the session if previous session fails?

3 Answers  

---

What are the reusable transforamtions?

1 Answers  

---

Design a mapping to load a target table with the following values from the above source?

0 Answers   Informatica,

---

Does an informatica transformation support only aggregate expressions?

0 Answers  

---