DataStage vs stored procedure(partitioned)

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
ds_is_fun
Premium Member
Premium Member
Posts: 194
Joined: Fri Jan 07, 2005 12:00 pm

DataStage vs stored procedure(partitioned)

Post by ds_is_fun »

Requirement - Only one record needed for a lookup.

Debating the advantage of datastage over stored procedures..datastage calls all the rows into the memory(in lookup or a join) vs a stored procedure that makes a variable call from a cursor limting to say only one required row. So how does datastage take a lead in performance over a stored procedure.

Disadvantages felt -
1. A stored procedure returns only a single record if a lookup needs to performed taking advantage of indexing too but I DS brings the whole column data into memory and takes advantage of the parallel partiioning.
Remember a database takes advantage of partitioning, indexing and parallel partitioning from Oracle 10g.

Thanks!
Post Reply