2 responses

24 05 2013

I recently fought through this issue as well. In my case, one of the stored procedure parameters A) was unused and B) had a default value, so I removed that parameter from the stored procedure invocation. I suspect that SQL Server did something behind my back to “optimize” the call by removing the unused parameter.

17 12 2012

I had a similar problem a while back:

Things can look good at design time and fall apart at run time, it seems. Anyway, I had to edit the XML code to get the evaluation to happen in the correct order.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


Get every new post delivered to your Inbox.

Join 306 other followers

%d bloggers like this: