BUG: RETURN Statement After an RPC Causes Extra Result Set

• Microsoft SQL Server version 4.2 for OS/2

SYMPTOMS

An extra result set is returned from SQL Server when a stored procedure containing an EXECUTE of a remote stored procedure, followed by a RETURN statement, is executed. This does not happen if there is no return statement following the execute of the remote stored procedure, or if a local stored procedure is executed instead of a remote one.

For example, executing the following stored procedure replicates the above problem:

   create proc rpcproc as
   execute <remote machine>...sp_who
   return
   go
   execute rpcproc
   go

WORKAROUND

Modify the stored procedure, if possible, to avoid the explicit RETURN statement following the call to execute the remote stored procedure. Also ensure your front-end application is handling the extra result set properly. A DB-LIBRARY (db-lib) front-end should always call dbresults until it returns NO_MORE_RESULTS.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 4.2 for OS/2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.