The following terms are defined in [MS-GLOS]:
Security Support Provider Interface (SSPI)
Session Multiplex Protocol (SMUX)
The following terms are specific to this document:
bulk insert: A method for efficiently populating the rows of a table from the client to the server.
client: A program that establishes connections for the purpose of sending requests.
column: A set of data composed of the same field from each row in a table.
Common Language Runtime User-Defined Type (CLR UDT): A data type created and defined by the user on a database server that supports SQL by using a .NET Framework common language runtime assembly.
data store: A repository for data.
data stream: A stream of data that corresponds to specific TDS semantics. A single data stream can represent an entire TDS message or only a specific, well-defined portion of a TDS message. A TDS data stream can span multiple network data packets.
delete: To remove a row from a table.
Distributed Transaction Coordinator (DTC): A service that coordinates transactions across multiple databases. For more information, see [MSDN-DTC].
final state: The application layer has finished communication and the lower layer connection should be disconnected.
initial state: A prerequisite for application layer communication. A lower layer channel which can provide reliable communication must be established.
insert: To add a row to a table.
Microsoft/Windows Data Access Components (MDAC/WDAC): With Microsoft/Windows Data Access Components (MDAC/WDAC), developers can connect to and use data from a wide variety of relational and nonrelational data sources. You can connect to many different data sources using Open Database Connectivity (ODBC), ActiveX Data Objects (ADO), or OLE DB. You can do this through providers and drivers that are built and shipped by Microsoft, or that are developed by various third parties. For more information, see [MSDN-MDAC].
Multiple Active Result Sets (MARS): A feature introduced in SQL Server 2005 that allows applications to have more than one pending request per connection. For more information, see [MSDN-MARS].
out-of-band: A type of event that happens outside of the standard sequence of events. Specifically, the idea that a signal or message can be sent during an unexpected time and will not cause any protocol parsing issues.
query: A character string expression sent to a data store that contains a set of operations that request data from the data store.
query notification: A feature introduced in SQL Server 2005 that allows the client to register for notification on changes to a given query result. For more information, see [MSDN-QUERYNOTE].
Remote Procedure Call (RPC): The direct invocation of a stored procedure or user-defined function on the server.
request: A TDS message initiated by a client and sent to a server.
response: A TDS message sent by a server to a client related to a previously issued request.
server: An application program that accepts connections to service requests by sending back responses. Any program might be capable of being both a client and a server. Use of these terms refers only to the role being performed by the program for a particular connection rather than to the program's capabilities in general.
SQL Server Native Client (SNAC): SNAC contains the SQL Server ODBC driver and the SQL Server OLE DB provider in one native dynamic link library (DLL) supporting applications using native-code APIs (ODBC, OLE DB, and ADO) to Microsoft SQL Server. For more information, see [MSDN-SNAC].
SPNEGO: Simple and Protected GSS-API Negotiation as defined by [RFC4178]. This mechanism is used by SSPI for negotiation.
SQL batch: A set of SQL statements.
SQL Server User Authentication (SQLAUTH): An authentication mechanism used to support user accounts on a database server that supports SQL. The username and password of the user account are transmitted as part of the login message that the client sends to the server.
SQL statement: A character string expression in a language the server understands.
structurally invalid: A data stream that does not follow the header defined, the rule for the specific message type defined in section 2, or both.
TDS session: A successfully established communication over a period of time between a client and a server on which the Tabular Data Stream (TDS) protocol is used for message exchange.
Unicode: The set of characters as defined by [UNICODE] that are encoded in UCS-2.
update: An add, modify, or delete operation of one or more objects or attribute values.
Virtual Interface Architecture (VIA): A high-speed interconnect requiring special hardware and drivers provided by third parties.
MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as described in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.