Answer Posted / 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.

What are the components of workflow manager?

1105

---

What is update strategy transform?

1113

---

What is Session and Batches?

1109

---

suppose we are using dynamic lookup cache and in lookup condition the record is succeeded but in target it is failed due to some reasons then what happened in the cache ?

7250

---

To import the flat file definition into the designer where should the flat file be placed?

1061

---

How do you load more than 1 max sal in each department through informatica or write sql query in oracle?

1584

---

What is an aggregator transformation?

1099

---

What is data movement mode in Informatica and difference between them?

1140

---

design of staging area?

2030

---

hi friends ... i have insurance project(informatica),can you please tell me how many table and mappings we need to use?and explain me.. thank you

9828

---

What is exclusive and normal mode for repository services?

1147

---

What is the difference between source qualifier transformations source filter to filter transformation?

1058

---

Differentiate between sessions and batches?

1021

---

COL1,COL2 ABC,1 XYZ,2 HERE IN COL2 VALUES 1,2 NOT STSANDARD(IE MEANS NOT FIXED VALUES LIKE OTHER SOME VALUES LIKE 10,20) O/P IS COL1,COL2 ABC,2 XYZ,1

1956

---

can anyone explain me about retail domain project in informatica?

7948

---