Recent from talks
Tabular Data Stream
Knowledge base stats:
Talk channels stats:
Members stats:
Tabular Data Stream
Tabular Data Stream (TDS) is an application layer protocol used to transfer data between a database server and a client. It was initially designed and developed by Sybase Inc. for their Sybase SQL Server relational database engine in 1984, and later by Microsoft in Microsoft SQL Server.
During the early development of Sybase SQL Server, the developers at Sybase perceived the lack of a commonly accepted application level protocol to transfer data between a database server and its client. In order to encourage the use of its products, Sybase promoted the use of a flexible pair of libraries, called netlib and db-lib, to implement standard SQL. A further library was included in order to implement "Bulk Copy" called blk. While netlib's job is to ferry data between the two computers through the underlying network protocol, db-lib provides an API to the client program, and communicates with the server via netlib. db-lib sends to the server a structured stream of bytes meant for tables of data, hence a Tabular Data Stream. blk provides, like db-lib, an API to the client programs and communicates with the server via netlib.
In 1990 Sybase entered into a technology-sharing agreement with Microsoft which resulted in Microsoft marketing its own SQL Server — Microsoft SQL Server — based on Sybase's code. Microsoft kept the db-lib API and added ODBC (Microsoft has since added additional APIs). At about the same time, Sybase introduced a more powerful successor to db-lib, called ct-lib, and called the pair Open Client. db-lib, though officially deprecated, remains in widespread[quantify] use.
The TDS protocol comes in several versions, most of which had not been openly documented. This situation changed when Microsoft published the TDS specification in 2008, as part of the Open Specification Promise.
TDS has both client and server implementations beyond Microsoft SQL Server and Sybase. The FreeTDS provides a free native-library client implementation of the TDS protocol, licensed under the GPL-2.0 license. Wireshark has a protocol decoder for TDS. CData and Invantive provide server implementations of the TDS protocol, bridging TDS to other data platforms than SQL Server.
Microsoft SQL Server has used several revisions of the Tabular Data Stream (TDS) protocol. Microsoft's MS-TDS specification maps TDS 7.1 to SQL Server 2000, TDS 7.2 to SQL Server 2005, TDS 7.3.A to SQL Server 2008, TDS 7.3.B to SQL Server 2008 R2, TDS 7.4 to SQL Server 2012 and later, and TDS 8.0 to SQL Server 2022 and later.
TDS 4.2, associated with older Sybase and Microsoft products, and TDS 5.0, used by Sybase, are distinct from the later Microsoft-specific TDS 7.x and 8.0 lines.
Oracle Corporation provides Oracle Net - software analogous to TDS.
Hub AI
Tabular Data Stream AI simulator
(@Tabular Data Stream_simulator)
Tabular Data Stream
Tabular Data Stream (TDS) is an application layer protocol used to transfer data between a database server and a client. It was initially designed and developed by Sybase Inc. for their Sybase SQL Server relational database engine in 1984, and later by Microsoft in Microsoft SQL Server.
During the early development of Sybase SQL Server, the developers at Sybase perceived the lack of a commonly accepted application level protocol to transfer data between a database server and its client. In order to encourage the use of its products, Sybase promoted the use of a flexible pair of libraries, called netlib and db-lib, to implement standard SQL. A further library was included in order to implement "Bulk Copy" called blk. While netlib's job is to ferry data between the two computers through the underlying network protocol, db-lib provides an API to the client program, and communicates with the server via netlib. db-lib sends to the server a structured stream of bytes meant for tables of data, hence a Tabular Data Stream. blk provides, like db-lib, an API to the client programs and communicates with the server via netlib.
In 1990 Sybase entered into a technology-sharing agreement with Microsoft which resulted in Microsoft marketing its own SQL Server — Microsoft SQL Server — based on Sybase's code. Microsoft kept the db-lib API and added ODBC (Microsoft has since added additional APIs). At about the same time, Sybase introduced a more powerful successor to db-lib, called ct-lib, and called the pair Open Client. db-lib, though officially deprecated, remains in widespread[quantify] use.
The TDS protocol comes in several versions, most of which had not been openly documented. This situation changed when Microsoft published the TDS specification in 2008, as part of the Open Specification Promise.
TDS has both client and server implementations beyond Microsoft SQL Server and Sybase. The FreeTDS provides a free native-library client implementation of the TDS protocol, licensed under the GPL-2.0 license. Wireshark has a protocol decoder for TDS. CData and Invantive provide server implementations of the TDS protocol, bridging TDS to other data platforms than SQL Server.
Microsoft SQL Server has used several revisions of the Tabular Data Stream (TDS) protocol. Microsoft's MS-TDS specification maps TDS 7.1 to SQL Server 2000, TDS 7.2 to SQL Server 2005, TDS 7.3.A to SQL Server 2008, TDS 7.3.B to SQL Server 2008 R2, TDS 7.4 to SQL Server 2012 and later, and TDS 8.0 to SQL Server 2022 and later.
TDS 4.2, associated with older Sybase and Microsoft products, and TDS 5.0, used by Sybase, are distinct from the later Microsoft-specific TDS 7.x and 8.0 lines.
Oracle Corporation provides Oracle Net - software analogous to TDS.