Home Dashboard Directory Help
Search

sp_sproc_columns fails if SET FMTONLY ON is executed first by danholmes


Status: 

Closed
 as Won't Fix Help for as Won't Fix


1
0
Sign in
to vote
Type: Bug
ID: 790100
Opened: 6/13/2013 6:58:02 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description


executing SET FMTONLY ON; exec sp_sproc_columns ... will fail with the following error message:

Msg 245, Level 16, State 1, Procedure sp_sproc_columns, Line 46
Conversion failed when converting the nvarchar value '%' to data type int.

This is important because Crystal (and probably other ODBC based data consumers) executes this proc this way (http://msdn.microsoft.com/en-us/library/aa177863(v=sql.80).aspx).

This mechanism was apparently changed in 2012 (http://msdn.microsoft.com/en-us/library/ms130945.aspx) but not in 2005 (http://msdn.microsoft.com/en-us/library/ms130945(v=sql.90).aspx).

I have added a bit more on the the affects of SET FMTONLY ON; on my blog
http://dnhlmssql.blogspot.com/2013/06/new-connect-item-spsproccolumns-fails.html
Details
Sign in to post a comment.
Posted by Microsoft on 7/18/2013 at 1:44 PM
Hello,

Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SQL Server. Thanks again for reporting the product issue and continued support in improving our product.

Sincerely,
Manbeen
Posted by Microsoft on 7/18/2013 at 1:44 PM
Hello,

Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SQL Server. Thanks again for reporting the product issue and continued support in improving our product.

Sincerely,
Manbeen
Sign in to post a workaround.