Lookup

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
Subhasree
Participant
Posts: 11
Joined: Fri Jul 27, 2007 12:12 am

Lookup

Post by Subhasree »

Hi All,

What is the difference between Normal and Sparse Lookup?
Im having a Source table containing 9 records and im doing a sparse lookup on target table containing 9 records.The lookup condition used is continue.The number of records from the output link is 387.How is it happening???
What is the concept of sparse lookup?In help i found that its doing a direct query on the database rather than from the buffer.But how that will be the cause for my job which is producing 387 records?
saikir
Participant
Posts: 92
Joined: Wed Nov 08, 2006 12:25 am
Location: Minneapolis
Contact:

Post by saikir »

Hi,

In Sparse lookup for every incoming input row, a SQL is fired on the Reference table. This is effective if the number of incoming rows are very less and reference table has a large number of rows (1:100). Refer the DataStage Parallel Job Advanced Developer Guide for more info.

Sai
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

There is not enough information to answer the question. How many nodes are in your configuration file? What partitioning algorithms are used on each link in your job design? Do all nine source records have a matching key in the reference data?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply