SQLNCLI creates invalid SQL against 2008(r2) when the parameters are refreshed - by danholmes

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 779618 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 2/20/2013 7:51:38 AM
Access Restriction Public

Description

the SQLNCL 9-11 produces incorrect syntax when it is refreshing the parameters from ADO.

The following events are shown in Profiler.
SQL:StmtStarting: SET NO_BROWSETABLE OFF
SQL:Stmtcompleted: SET NO_BROWSETABLE OFF
SQL:BatchCompleted: SET NO_BROWSETABLE OFF
SP:StmtStarting:  select        PROCEDURE_CATALOG ...
SP:StmtCompleted:  select        PROCEDURE_CATALOG ...
RPC:Completed: exec [?].[sys].sp_procedure_params_90_rowset N'spCustomerSelect',1,NULL,NULL
SQL:StmtStarting: SET NO_BROWSETABLE ON
SQL:Stmtcompleted: SET NO_BROWSETABLE ON
SQL:BatchCompleted: SET NO_BROWSETABLE ON
User Error Message:  Procedure or function 'spCustomerSelect' expects parameter '@ContextStr', which was not supplied.
RPC:Completed: exec spCustomerSelect default,default,default

In addition to these sequences, the following thread in the forum details a profiler trace that is similar and also produces an error based on a metadata request from the driver.
http://social.msdn.microsoft.com/Forums/en-US/sqldataaccess/thread/0f288a6d-da06-4730-8ed5-db24a036998e
Sign in to post a comment.
Posted by danholmes on 8/8/2013 at 9:56 AM
i just tried this again and got the same error. Did you create the database and the script that was supplied?
Posted by Microsoft on 4/15/2013 at 4:29 PM
Thanks for your feedback. Unfortunately we are not able to reproduce the issue.