Multiple Instance Usage - Best Practices
Posted: Tue May 22, 2007 7:03 am
I've run into a situation where I need a job that can be called at many different times by many different control jobs. The chance that the job could be called at the same time by two different control jobs is VERY likely.
Therefore, I looked into making the job a multiple instance job. This sounded like a good idea until I realized that every instance has to have a unique invocation id and the jobs do not clean themselves up after running. I could make this work by having the control jobs create a numeric datetime string as the invocation id, but how do you handle the cleanup?
Would like to hear tips about ultilizing multiple instance the best way.
thanks,
Greg
Therefore, I looked into making the job a multiple instance job. This sounded like a good idea until I realized that every instance has to have a unique invocation id and the jobs do not clean themselves up after running. I could make this work by having the control jobs create a numeric datetime string as the invocation id, but how do you handle the cleanup?
Would like to hear tips about ultilizing multiple instance the best way.
thanks,
Greg