January 19, 2010 at 9:35 am
I have two servers that each has a SSIS packages on them.
Server A - Server - B - Server C
pack1 pack2 pack3
If pack1 fails I don't want pack2 or pack3 to run. Or if pack 2 fails I don't want pack3 to run...and so on. Is it possible for SQL server not to execute theses Jobs unless the one before it runs correctly?
Chad
January 19, 2010 at 9:44 am
I believe it would depend on what your packages are doing exactly. I would probably look at checking for a flag or some type of value if the package was successful.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
January 19, 2010 at 12:39 pm
You can query msdb.dbo.sysjobhistory to see if the job was successful or not. If you go this route, you'll need to create a linked server to check the job history whatever server contains the job. If got some processes that utilize this and it works quite well.
January 19, 2010 at 1:30 pm
how are you deploying your SSIS packages?
1. Deploying to a dtsx file on a file server
2. Deploying on SQL server under MSDB
3. Calling dtexec to call specific file on file server or sql server?
it depends. but bottom like is you can if you included them into one schedule and used the onFailure action. imho
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply