sparse lookup partitioning

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
dnat
Participant
Posts: 200
Joined: Thu Sep 06, 2007 2:06 am

sparse lookup partitioning

Post by dnat »

Hi,

Does changing the partition for a Sparse lookup have any effect, since it is directly firing the queries to the DB?. I have all the stages with Auto partition, but just wanted to know whether changing the partition for a sparse lookup will have any impact.
Top
miwinter
Participant
Posts: 396
Joined: Thu Jun 22, 2006 7:00 am
Location: England, UK

Post by miwinter »

No, this should have no effect on the lookup behaviour whatsoever, though I would have some suspicion that using Entire might result in multiple matching, if your lookup runs in parallel. Definitely best you stick with Auto - is there some reason why you are thinking of changing this?
Last edited by miwinter on Wed Aug 05, 2009 3:35 am, edited 1 time in total.
Mark Winter
<i>Nothing appeases a troubled mind more than <b>good</b> music</i>
Top
dnat
Participant
Posts: 200
Joined: Thu Sep 06, 2007 2:06 am

Post by dnat »

Hi, Thanks. I am not sure whether Auto-partition is best to use. So i thought i would use hash partition. But just wanted to clarify whether it is necessary to change for sparse lookup.
Top
Post Reply

Return to “IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)”