"MS-TDS协议2023最新版及使用规范V34.0"

需积分: 5 119 浏览量更新于2023-11-24 收藏 7.4MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源推荐

16 / 226

[MS-TDS] - v20230410

Tabular Data Stream Protocol

Release: April 10, 2023

1.4 Relationship to Other Protocols

The Tabular Data Stream (TDS) protocol depends upon a network transport connection being

established prior to a TDS conversation occurring (the choice of transport protocol is not important to

TDS).

TDS depends on Transport Layer Security (TLS)/Secure Socket Layer (SSL) for network channel

encryption. In the TDS 7.x version family, TLS/SSL is optional and the negotiation of the encryption

setting between the client and server and the initial TLS/SSL handshake are handled in the TDS layer.

Introduced in the TDS 8.0 version, TLS is mandatory and is established in the lower layer before TDS

begins functioning.

If the Multiple Active Result Sets (MARS) feature [MSDN-MARS] is enabled, the Session

Multiplex Protocol (SMP) [MC-SMP] is required.

This relationship is illustrated in the following figure.

Figure 2: Protocol relationship

1.5 Prerequisites/Preconditions

This protocol can be used after the client has discovered the server and established a network

transport connection for use with TDS.

In the TDS 7.x version family, no security association is assumed to have been established at the

lower layer before TDS begins functioning. In the TDS 8.0 version, such a security association is

assumed.

For Security Support Provider Interface (SSPI) [SSPI] authentication to be used, SSPI support

needs to be available on both the client and server machines. For channel encryption to be used,

TLS/SSL support needs to be present on both client and server machines, and a certificate suitable for

encryption has to be deployed on the server machine.

For federated authentication to be used, a library that provides federated authentication support or

an equivalent needs to be present on the server, and the client needs to be able to generate a token

for federated authentication.

17 / 226

[MS-TDS] - v20230410

Tabular Data Stream Protocol

Release: April 10, 2023

1.6 Applicability Statement

The TDS protocol is appropriate for use to facilitate request/response communications between an

application and a database server in all scenarios where network or local connectivity is available.

1.7 Versioning and Capability Negotiation

This protocol includes versioning issues in the following areas.

 Supported Transports: This protocol can be implemented on top of any network transport

protocol as discussed in section 2.1.

 Protocol Versions: The TDS protocol supports the TDS 7.x version family (which is composed of

explicit versions TDS 7.0, TDS 7.1, TDS 7.2, TDS 7.3, and TDS 7.4) and the TDS 8.0 explicit

version.

In TDS 7.x, the explicit version is negotiated as part of the LOGIN7 message data stream, as

described in section 2.2.6.4.

In TDS 8.0, the explicit version must be identified from the TLS handshake by using an

Application-Layer Protocol Negotiation (ALPN) TLS extension [RFC7301]. If ALPN is not present,

the server must assume the TDS 8.0 version has been sent. Version information sent in the

LOGIN7 message data that is later in the flow does not have to be specified and should be ignored

by both the client and server.

Aspects of later versions of the TDS protocol that do not apply to earlier versions are identified in

the text.

Note After a protocol feature is introduced, subsequent versions of the TDS protocol support that

feature until that feature is removed.

 Security and Authentication Methods: The TDS protocol supports SQL Server User

Authentication (SQLAUTH). The TDS protocol also supports SSPI authentication and indirectly

supports any authentication mechanism that SSPI supports. The use of SSPI in TDS is defined in

sections 2.2.6.4 and 3.2.5.2. The TDS protocol also supports federated authentication. The use

of federated authentication in TDS is defined in sections 2.2.6.4 and 3.2.5.

 Localization: Localization-dependent protocol behavior is specified in sections 2.2.5.1.2 and

2.2.5.6.

 Capability Negotiation: This protocol does explicit capability negotiation as specified in this

section.

In general, the TDS protocol does not provide facilities for capability negotiation because the complete

set of supported features is fixed for each version of the protocol. Certain features such as

authentication type are not usually negotiated but rather are requested by the client. However, the

protocol supports negotiation for the following two features:

 Channel encryption: In TDS 7.x, the encryption behavior that is used for the TDS session is

negotiated in the initial messages exchanged by the client and the server. In TDS 8.0, encryption

is mandatory and is established prior to initial messaging by the client and the server.

 Authentication mechanism for integrated authentication identities: The authentication

mechanism that is used for the TDS session is negotiated in the initial messages exchanged by the

client and the server.

For more details about encryption behavior in TDS 7.x and about how the client and server negotiate

between SSPI authentication and federated authentication, see the PRELOGIN description in section

2.2.6.5.

19 / 226

[MS-TDS] - v20230410

Tabular Data Stream Protocol

Release: April 10, 2023

2 Messages

The formal syntax of all messages is provided in Augmented Backus-Naur Form (ABNF) [RFC4234],

with the addition of the following:

 underscore ("_") – a valid character within an identifier.

 "%x00" – a valid value.

 "%b0" – a valid value.

2.1 Transport

The TDS protocol does not prescribe a specific underlying transport protocol to use on the Internet or

on other networks. TDS 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, any TDS packet sent from a TDS client to a TDS server MUST be contained within a

single transport data unit. Any additional mapping of TDS data onto the transport data units of the

protocol in question is outside the scope of this specification.

The current version of the TDS protocol has implementations over the following transports, except as

indicated:<2>

 TCP [RFC793].

 A reliable transport over the Virtual Interface Architecture (VIA) interface [VIA2002] can be

used in only TDS 7.0, TDS 7.1, TDS 7.2, and TDS 7.3.<3>

 Named Pipes [MSDN-NP].

 Shared memory [MSDN-TDSENDPT].

 Optionally, the TDS protocol has implementations for the following protocols on top of the

preceding transports:

 Transport Layer Security (TLS)/Secure Socket Layer (SSL) [RFC2246] [RFC5246] [RFC6101],

in case TLS/SSL encryption is negotiated in TDS 7.x.

 TLS [RFC8446], in case TLS encryption is established in TDS 8.0.

 Session Multiplex Protocol (SMP) [MC-SMP], in case the Multiple Active Result Sets

(MARS) feature [MSDN-MARS] is requested.

2.2 Message Syntax

Character data, such as SQL statements, within a TDS message is in Unicode, unless the character

data represents the data value of an ASCII data type, such as a non-Unicode data column. A character

count within TDS is a count of characters, rather than of bytes, except when that character count is

explicitly specified as a byte count.

2.2.1 Client Messages

Messages sent from the client to the server are as follows:

 Pre-Login

20 / 226

[MS-TDS] - v20230410

Tabular Data Stream Protocol

Release: April 10, 2023

 Login

 Federated Authentication Token

 SQL Batch

 Bulk Load

 Remote Procedure Call

 Attention

 Transaction Manager Request

These messages are briefly described in the sections that follow. Detailed descriptions of message

contents are in section 2.2.6.

2.2.1.1 Pre-Login

Before a login occurs, a Pre-Login handshake occurs between client and server, setting up contexts

such as encryption and MARS-enabled. For more details, see section 2.2.6.5.

2.2.1.2 Login

When the client makes the determination to establish a TDS protocol connection with the server side,

the client sends a Login message data stream to the server. The client can have more than one

connection to the server, but each connection is established separately in the same way. For more

details, see section 2.2.6.4.

After the server receives the login record from the client and, if necessary, performs subsequent

authentication handshakes (such as when SSPI [SSPI] or federated authentication is used), the

server notifies the client that it has either accepted or rejected the connection request. For more

details, see section 3.3.5.1.

2.2.1.3 Federated Authentication Token

When the client indicates in the Login record that federated authentication<4> is to be used but

that the intended client library needs additional information from the server to generate a federated

authentication token, if the server supports federated authentication that uses that client library, the

server responds with a token that the client uses to perform federated authentication. The client then

generates and sends a tokenless Federated Authentication Token message that contains binary

authentication data that is generated by the federated authentication library. For more details, see

section 2.2.6.3.

After the server receives the Federated Authentication Token message from the client, the server

notifies the client that it has either accepted or rejected the connection request. For more details, see

section 3.3.5.

2.2.1.4 SQL Batch

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 can span more than one TDS packet. For more details, see section 2.2.6.7.

剩余225页未读，继续阅读

跟着袜总有肉吃

粉丝: 5
资源: 2

会员权益专享

"MS-TDS协议2023最新版及使用规范V34.0"

MS-TDS协议规范最新版[v20120328]

TDS协议分析程序

TDS通信协议

tds协议 如何判断sql执行错误

tds协议 如何取出执行的sql语句

tds协议 如何根据type判断sql执行错误

tds协议 详细说明如何根据type判断sql执行错误

tds协议 如何判断sql执行时延

tds board v1.0

传入的表格格式数据流(TDS)协议流不正确。MARS TDS 头包含错误

传入的表格格式数据流(TDS)协议流不正确

tds 协议sql响应时延如何计算

onvif discovery代码

解释以下代码 uint16_t calculateTDS(uint16_t adcValue) { float voltage = adcValue * TDS_VREF / 4096.0; float tdsValue = voltage / (TDS_VREF / TDS_RANGE) * TDS_FACTOR; return (uint16_t)tdsValue; }

编写一段arduino代码，实现功能：测量2组温度，3处水位状态，一处水质的TDS，

string returnContent = UploadLine(gd2, "http://192.168.10.56:8020/clover-tds/external/order/deleteFinishOrder");

tds传感器ADC转换代码

function V=TDS(v); for t=t(n) if t<200 v=30 elseif 200<t && t<400 v=60 elseif 400<t && t<800 v=45 else 800<t && t<1200 v=35 end

会员权益专享

最新资源

tds协议如何判断sql执行错误

tds协议如何取出执行的sql语句

tds协议如何根据type判断sql执行错误

tds协议详细说明如何根据type判断sql执行错误

tds协议如何判断sql执行时延