Can't Operate FailPackOnFailure property
after the execute SQL task I guess you have more tasks connected to it via precedence constraint(green arrow). Double click it and set it to
completion instead of default success.My Blog | Ask Me
February 8th, 2011 5:15pm
It's the last task in the conatiner - so it does not have any arrows coming out of it.
I don't what to change the green arrow coming out of the it's container since I have several tasks in it and i DO want the container to fail if one of the other tasks fail.
Any other idea?Erez K
Free Windows Admin Tool Kit Click here and download it now
February 8th, 2011 5:23pm
Until you find it you can modify it to auto restart as in this article:
http://social.technet.microsoft.com/wiki/contents/articles/automatic-restart-of-ssis-packages-after-failover-or-failure.aspx.
Another option is to use checkpoints to restart from point of failure:
http://msdn.microsoft.com/en-us/library/ms140226.aspx
One more, in-depth, post on the Checkpoints:
https://community.altiusconsulting.com/blogs/altiustechblog/archive/2009/09/09/ssis-2008-package-restarting-and-checkpoints.aspxArthur My Blog
February 8th, 2011 5:40pm
Hi,
I have a SQL Execute Task which sometimes fails due to Deadlock.
When it fails and I execute the whole package again - It runs OK.
My main problem is that It's failure fails the whole package.
Until I find the cause for this deadlock I don't want it to fail the whole package.
The "FailPackageOnError" property of this SQL Execute task is set to FALSE - however, when deadlock occurs it still fails the whole package.
How can I make the package "ignore" this specific task in case it fails?
Additional info about this task:
MaxErrorCount = 1
ForcedExecutionValue = 0
ForceExecutionValue = False
Does anyone have an idea?
Thanks!
DavidErez K
Free Windows Admin Tool Kit Click here and download it now
February 8th, 2011 7:06pm