Surrogate Key Suggestions from the experts
Posted: Thu Dec 09, 2004 1:38 pm
All:
I am a DataStage novice so please provide as detailed feedback as you see fit and have time for; I am researching this but figured I would ask you, the expert DataStage users/developers, for your suggestions.
I have a Custom Stage written in C++/Oracle Pro*C/C++ that fetches a sequence value (NEXTVAL) from the database; my research on its usage suggests that its only function is to generate a surrogate key.
The stage takes an input data stream, the Oracle information (sequence name, schema, password, sid) and simply tacks on the nextval; if you picture it, it is one icon.
Having said that, I am looking to replace that one icon with a more "maintenace friendly solution". Could you please provide suggestions on possible approaches to replace the one icon with another icon that performs the same function (getting the nextval from Oracle in a datastream providing the sequence name).
Please keep in mind that because the existing stage is an Orchestrate based routine it comes with all the apparent "parallelism" that is part of the Parallel Extender and that I am looking to maintain the performance levels if possible.
Thank you,
Stephen de Vries
I am a DataStage novice so please provide as detailed feedback as you see fit and have time for; I am researching this but figured I would ask you, the expert DataStage users/developers, for your suggestions.
I have a Custom Stage written in C++/Oracle Pro*C/C++ that fetches a sequence value (NEXTVAL) from the database; my research on its usage suggests that its only function is to generate a surrogate key.
The stage takes an input data stream, the Oracle information (sequence name, schema, password, sid) and simply tacks on the nextval; if you picture it, it is one icon.
Having said that, I am looking to replace that one icon with a more "maintenace friendly solution". Could you please provide suggestions on possible approaches to replace the one icon with another icon that performs the same function (getting the nextval from Oracle in a datastream providing the sequence name).
Please keep in mind that because the existing stage is an Orchestrate based routine it comes with all the apparent "parallelism" that is part of the Parallel Extender and that I am looking to maintain the performance levels if possible.
Thank you,
Stephen de Vries