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.

How can i explain my project architecture in interview..? in Igate asked me tell me your project flow from source to target..?

1 Answers   Ameri Group, CGI, CTS, HCL, iGate, TCS, Wipro,

---

can anyone explain me about sales project in informatica?

8 Answers   MBT, Satyam,

---

How informatica recognizes mapping?

2 Answers   CTS,

---

what type of transformation is not supported by mapplets?

4 Answers   CTS,

---

I am using mapping variable, when i am running a session,before it has 10000 records, after completion of session what about value of mapping variable?

1 Answers  

---

how many types of dimensions are available in informatica?

0 Answers  

---

what is the method of error handling when session is running?

1 Answers   TCS,

---

how i will stop my workflow after 10 errors

2 Answers   HP,

---

in static and dynamic which one is better

2 Answers  

---

What is an unconnected transformation?

0 Answers   Informatica,

---

What is session task and command task?

0 Answers  

---

what is plsql table?

2 Answers  

---