By the way, I tried the repro on the July CTP of SQL 2008, and the error
does not occur there, but the procedure completes successfully.

--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

On Sep 28 2007, 05:28 pm, Erland Sommarskog <esquel (AT) sommarskog (DOT) se> wrote
in news:Xns99B9EFAA31154Yazorman (AT) 127 (DOT) 0.0.1:

The RECOMPILE hint is there to make it consistently reproducible. Before I
added that, the issue only occurred intermittently (apparently, when the
function's plan had to be recompiled).

I wish I had seen that in the beginning, at least I could be certain it's a
real problem.

I updated the bug report to include these two bits of information.

--
remove a 9 to reply by email

On Sep 28 2007, 05:42 pm, Erland Sommarskog <esquel (AT) sommarskog (DOT) se> wrote in
news:Xns99B9F1E3FC5AEYazorman (AT) 127 (DOT) 0.0.1:

I hope it does not mean that they won't bother fixing it in 2005...

--
remove a 9 to reply by email

Dimitri Furman (dfurman (AT) cloud99 (DOT) net) writes:
I could be that it's fixed in Katmai "by accident", but it could also
be the case that the issue is known, but the fix is deemed to risky to
implement in SQL 2005.

I found this KB Article: http://support.microsoft.com/kb/923605, but this
appears to relate to a fix for SP1. Nevertheless, the Symptoms section
says "This problem occurs if table variables are used in a transaction."


--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx