jjefferson
Technical User
I have an SSIS 2008 package that is working fine. There is a script task at the very beginning that looks for the file it wants to import. I have a precedence constraint between that and the next step to test the success of the script task.
When I run this manually from VS, it works fine and stops execution if the file does not exist.
I've moved this onto the server now, and set up a SQL Agent job to execute the package on an hourly basis. It is working fine here, too, with one small annoyance.
When there is no file to import, the job history records a failure. Generally this is okay, except that there is no distinction between this (an expected condition) and a "true" failure.
Any recommendations on what I can either add to the package to exit as if everything succeeded from just this one task in the flow (don't want to exit gracefully elsewhere as that would be a true failure I would want to see), or add something to the Agent job steps perhaps?
Thanks!
When I run this manually from VS, it works fine and stops execution if the file does not exist.
I've moved this onto the server now, and set up a SQL Agent job to execute the package on an hourly basis. It is working fine here, too, with one small annoyance.
When there is no file to import, the job history records a failure. Generally this is okay, except that there is no distinction between this (an expected condition) and a "true" failure.
Any recommendations on what I can either add to the package to exit as if everything succeeded from just this one task in the flow (don't want to exit gracefully elsewhere as that would be a true failure I would want to see), or add something to the Agent job steps perhaps?
Thanks!