INF: SQL Server RPC Uses Make/Break Connections

Last reviewed: May 1, 1997
Article ID: Q138515

The information in this article applies to:
  • Microsoft SQL Server, version 6.0

SUMMARY

Microsoft SQL Server versions 4.21 and 6.0 use make or break connections for executing server-to-server Remote Procedure Calls (RPCs). This means the RPC connection is not maintained after its execution. The SQL Server 4.2 documentation incorrectly indicates that RPC connections may be maintained.

MORE INFORMATION

SQL Server for Windows NT platforms including versions 4.21 and 6.0 implements RPCs through DB-Library connections, which allow server-to-server RPCs using any IPCs supported by SQL Server, not just named pipes, as in the case of OS/2 SQL Server versions. The RPC connections are immediately terminated after their executions, and it is not possible to maintain the connections with the current versions of SQL Server.

In the SQL Server 4.2 "System Administrator's Guide," page 267 and 268, section "Setting the Server Option," it is incorrectly stated that you can configure the SQL Server to either maintain the RPC connection or allow it to timeout. If you try to set this option, SQL Server 4.21 will not give you any error, but the RPC behavior is not affected.


Additional query words: sql6 winnt timeout sp_serveroption
Keywords : kbusage SSrvDoc_Err SSrvLan
Version : 4.21 6.0
Platform : WINDOWS
Issue type : kbdocerr


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 1, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.