title: MS SQL: Suppress return value of stored procedure called in stored procedure
body: <p>I think I have the same problem as kcrumley describes in the question "<a href="https://stackoverflow.com/questions/107585/problem-calling-stored-procedure-from-another-stored-procedure-via-classic-asp">Problem calling stored procedure from another stored procedure via classic ASP</a>". However his question does not really include an solution, so I'll give it another shot, adding my own observations:</p>
  
  <p>I have two stored procedures:</p>
  
  <pre><code>CREATE PROCEDURE return_1 AS BEGIN
      SET NOCOUNT ON;
      SELECT 1
  END
  
  CREATE PROCEDURE call_return_1_and_return_2 AS BEGIN
      SET NOCOUNT ON;
      EXEC return_1
      SELECT 2
  END
  </code></pre>
  
  <p>Note that both procedures contain "SET NOCOUNT ON". When I execute "call_return_1_and_return_2" I still get two record sets. First the value 1, then the value 2.</p>
  
  <p>That throws ASP (classic VBScript ASP) off the tracks.</p>
  
  <p>Any hints on how I can suppress the first result set? Why is it there even with NOCOUNT?</p>
  
  <p>Skipping the first record set in ASP is not an option. I need a "database only" solution.</p>