2.1 Transport

The TDS 4.2 protocol does not prescribe a specific underlying transport protocol to use on the Internet or on other networks. This protocol only presumes a reliable transport that guarantees in-sequence delivery of data.

The chosen transport can be either stream-oriented or message-oriented. If a message-oriented transport is used, then any TDS 4.2 packet sent from a TDS 4.2 client to a TDS 4.2 server MUST be contained within a single transport data unit. Any additional mapping of TDS 4.2 data onto the transport data units of the protocol in question is outside the scope of this specification.

The TDS 4.2 protocol has implementations over the following transports:

  • TCP. For more details, see [RFC793].

  • Named Pipes in message mode. For more details, see [MSDN-NP].<1>

  • Optionally, the TDS 4.2 protocol has implemented TLS (for more details, see [RFC2246]) and SSL on top of the preceding transports, in case TLS/SSL encryption is negotiated.