Answer Posted / subhash

Normal lookup will provide data for an in-memory look up
whereas Sparse lookup will access the database directly.
Normal might provide poor performance when the reference
data is huge as it has to load large data into memory.
In such scenarios a join stage may work better(It will put
the data onto an internal dataset file for each link,
and then do the join based on the data provided). If your
stream/source data is small then a sparse lookup is
suggested
as a row is retrieved from the database for each input row
instead of the full reference data being brought into
memory.
Sparse lookup sends individual SQL statement for every
incoming row (If stream/source data is huge you can imagine
the number
of times it has to hit DB and hence the down side on
performance). It can be used when you want to get the next
sequence
number from your database (Again expensive overhead on your
job as noted before). Also note that sparse lookup is only
available for DB2 and Oracle. Normal Lookup stage can have
multiple reference link but Sparse can only have one
reference
link. When normal is used it is a good practice to choose
less volume data as reference data.

Can you explain link buffering?

1179

---

how to delete one row in target dataset

3122

---

What are the difference types of stages?

1215

---

Define meta stage?

1202

---

How do you reject records in a transformer?

1124

---

what is use of SDR function?

5173

---

Triggers,VIEW,Procedures

1220

---

What is meta stage?

1182

---

What are the different layers in the information server architecture?

1124

---

What are the enhancements made in datastage 7.5 compare with 7.0?

1148

---

Difference between in process and inter process?

1236

---

What are the important features of datastage?

1127

---

how to implement scd2 in datastage 7.5 with lookup stage

5605

---

What are stage variables, derivations and constants?

1226

---

What all are the different way to run a job?

1094

---