Getting Job Run Statistics
Posted: Thu Feb 12, 2009 10:21 pm
We have huge number of jobs which is already there in production, and now a requirement came to capture the job run statistics to a table.
We can do it , by writing a seperate job and call that in the after job subroutine, But this requires , changing all the jobs. I want to achieve this with minimum impact.
And already , in all our jobs we are using a shared container, for capturing the last run dttm, and it is called after the target insert. We have a seperate path for target update also.
So , I want to know ,if i write a routine and call that in a shared container, will solve my issue. I am having doubt here because, at run time, Shared Container, will also be treated as a part of job, and if i check for job status, it will show as running only.
what will be the best approach for handling this, with minimal impact?
We can do it , by writing a seperate job and call that in the after job subroutine, But this requires , changing all the jobs. I want to achieve this with minimum impact.
And already , in all our jobs we are using a shared container, for capturing the last run dttm, and it is called after the target insert. We have a seperate path for target update also.
So , I want to know ,if i write a routine and call that in a shared container, will solve my issue. I am having doubt here because, at run time, Shared Container, will also be treated as a part of job, and if i check for job status, it will show as running only.
what will be the best approach for handling this, with minimal impact?