Separating Extract, Transformation and Load to three or more jobs, in order to in case of failure of some step, the previous steps can be reused. That sounds good in theory. Could any one tell where is the practice documented?
HI,
May be the function of calling the jobs using scritps can be verticalized.
Like you can try segregating the Extraction through a seperate script and transfromation through separate and like wise. so that the restrat point gets bifurcated.
Provided the tracability matrix should be perfect among jobs.
If I understand the problem, it isn't a Best practice that is the problem, but your tool/method to schedule and run your jobs that is the problem.
We use our Mainframe scheduling tool to run our DataStage jobs. This tool allows us to rerun jobs. I guess I just have it a little easier then some of you.
Either way it sounds like you have one heck of a mess.
Best of luck.
Sounds like some more thought needs to go into the design of your control structures and restart points. It's all doable, and gracefully. But it must be designed with care.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
In order to split ETL to E.T.L, a integrated job can always be built first as ETL. When the job is tested, it can be split to 3, 4, even 20s E.T.L jobs, to make it confirmed to the practice and the maintenance and support more challenge, that's the best practice?