Friday, March 23, 2012

ForceExecutionResult doesn't do what its supposed to.

[Microsoft follow-up]

All,

According to BOL the ForceExecutionResult property can be used to imitate real-time failure (http://msdn2.microsoft.com/en-us/library/microsoft.sqlserver.dts.runtime.dtsforcedexecresult.aspx).

However, I've just done a very simple test and this appears to not be the case. Here's the repro:

    Start a new package Drag on a Sequence Container Set the sequence container property ForceExecutionResult='Failure'

When you run the package the sequence container will complete successfully. As far as I can see its not supposed to.

Any comments?

Thanks

Jamie

I've just dragged a script task onto the same package. Opened the script and closed it again to make sure it compiles. Set ForceExecutionResult='Failure'.

When I run the package the script task fails. This is the behaviour I would expect so why is the Sequence Container different?

We have seen problems in the past with unexpected Sequence Container behaviour: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1875222&SiteID=1&mode=1

This is a bug as far as I can tell.

-Jamie

|||

Hmm... Interesting...

Trying it with a data flow task or a script tasks, it shows a failure, but with the sequence container it succeeds.

Looks like a bug in the sequence container?

BobP

|||

BobP - BIM wrote:

Hmm... Interesting...

Trying it with a data flow task or a script tasks, it shows a failure, but with the sequence container it succeeds.

Looks like a bug in the sequence container?

BobP

Definitely. I'm waiting on a reply from Microsoft befroe I submit it to Connect.

-Jamie

|||

Setting ForcedExecutionResult=Failure doesn't produce container failures on a sequence container... or a for loop, or a foreach loop, or the package itself, or an event handler. Seems like a bug.

|||I just went through the codes and seems like we only apply the ForceExecutionResult value for Tasks, not containers. Package, Sequence, Foreach Loop, and For Loop are all in the container category so the property does not get apply to them. It seems like a bug to me also.|||

Cho Yeung - msft wrote:

I just went through the codes and seems like we only apply the ForceExecutionResult value for Tasks, not containers. Package, Sequence, Foreach Loop, and For Loop are all in the container category so the property does not get apply to them. It seems like a bug to me also.

Hi Cho,

TaskHost is in the container category as well so its definitely a bug.

Do you need me to submit it on Connect?

-Jamie

|||I am going to file a bug internally. Thanks for bringing this up|||It is better to have Jamie open the bug so he can stay in the loop.|||

Bob Bojanic - MSFT wrote:

It is better to have Jamie open the bug so he can stay in the loop.


Thanks Bob. Its done.

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=288294

-Jamie

sql

No comments:

Post a Comment