July 14, 2014 at 6:41 am
Hi All,
I have a master SSIS package which calls multiple other SSIS packages. One of these sub-packages fails periodically because the source system is down. We do not want the master package to fail because of this issue.
When we run the master package using visual studio it runs as intended. However, when we put it in a SQL Agent job, and schedule the process, the job step lists as an error and stop.
We do want the job step to error if any of the other 4 sub-packages fail. Short of taking this one sub-step out and running it as it's own job step, does anyone know what has to be set in the master SSIS or sub-package which will return the needed status for the SQL Agent job to continue on running?
Thanks!
July 14, 2014 at 7:39 am
In the job that runs, edit the step and go to the advanced tab and set "On Failure Action:" to "Quit the job reporting success"
July 14, 2014 at 7:41 am
I do want that step to fail in other situations. That is the catch, out of 5 possible failures I want 1 of them to count as a success rather than failure, while 4 still need to fail the job step.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply