January 15, 2012 at 6:08 am
As far as i know, there is no any way to force the job success. maybe you have to do it by your logical side.
January 15, 2012 at 7:16 am
I think you could wrap the original call into a TRY ... CATCH block and don't raise an error at the CATCH section.
January 15, 2012 at 7:24 am
I also using same to get rid of repeated notification.
January 16, 2012 at 3:23 am
Paul Bukowski (1/15/2012)
For now, I manually create a new dummy step (last step) in the job, like say select getdate() and then execute that step, which will force the job to be successful.
It works, but it's not a "clean" technique. Be sure to document it properly.
My vote goes to TRY/CATCH.
-- Gianluca Sartori
Viewing 4 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply