Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>That would be because SSMS does not call an RPC but a batch. There is no way in fact to call a RPC from SSMS since you cannot declare a <em>parameter</em>, which is what differentiate an RPC call from a batch call in <a href="http://msdn.microsoft.com/en-us/library/dd304523%28prot.20%29.aspx" rel="nofollow">TDS</a>:</p> <blockquote> <p><a href="http://msdn.microsoft.com/en-us/library/dd357447%28prot.20%29.aspx" rel="nofollow">2.2.1.3 SQL Batch</a> To send a SQL statement or a batch of SQL statements, the SQL batch, represented by a Unicode string, is copied into the data section of a TDS packet and then sent to the database server that supports SQL. A SQL batch may span more than one TDS packet. See section 2.2.6.6 for additional detail</p> <p><a href="http://msdn.microsoft.com/en-us/library/dd303353%28prot.20%29.aspx" rel="nofollow">2.2.1.5 Remote Procedure Call</a> To execute a remote procedure call (RPC) on the server, the client sends an RPC message data stream to the server. This is a binary stream that contains the RPC name or numeric identifier, options, <strong>and parameters</strong>. RPCs MUST be in a separate TDS message and not intermixed with SQL statements. There can be several RPCs in one message. See section 2.2.6.5 for additional details.</p> </blockquote> <p>So monitor instead for the <a href="http://msdn.microsoft.com/en-us/library/ms176010.aspx" rel="nofollow"><code>SQL:BatchCompleted</code></a> event and you'll see your SSMS statement(s).</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload