1/19/2012 0.1.2 None No changes to the meaning, language, or formatting of the technical content. 2/23/2012 0.1.2 None No changes to the meaning, language, or formatting of the technical content. 3/27/2012 0.1.2 None No changes to the meaning, language, or formatting of the technical content. 5/24/2012 0.1.2 None No changes to the meaning, language, or formatting of the technical content. 6/29/2012 1.0 Major Updated and revised the technical content. 7/16/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2012 2.0 Updated and revised the technical content.
10/23/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 3/26/2013 2.0 None No changes to the meaning, language, or formatting of the technical content. 6/11/2013 2.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 2.0 None No changes to the meaning, language, or formatting of the technical content. 12/5/2013 2.0 None No changes to the meaning, language, or formatting of the technical content. 2/11/2014 3.0 Major Updated and revised the technical content. 5/20/2014 3.0 None No changes to the meaning, language, or formatting
of the technical content. 5/10/2016 4.0 Major Significantly changed the technical content. 8/16/2017 5.0 Major Significantly changed the technical content. 3/16/2018 5.1 Minor Clarified the meaning of the technical content.
Stream (TDS) version 4.2 protocol protocol that is used to transfer Transact-SQL requests and responses between clients and database products. The TDS 4.2 protocol provides for: Authentication and channel encryption negotiation. Specification of requests in SQL (including bulk insert). . Return of data. Transaction manager requests. Session Multiplex protocol (SMP) This protocol is used between clients and database servers to multiplex database communication sessions over a single reliable transport connection. SQL Server Resolution Protocol (SSRP) This protocol is used by clients to locate a named database server instance and to enumerate available database server instances. Tabular Data Stream (TDS) protocol This protocol is an application-level protocol that is used to transfer requests and responses between clients and database
Master Data Services The following protocols are used by Master Data Services (MDS). Protocol Description Reference Master Data Services web service This protocol is used when managing or editing any data or containers for data within the Master Data Services (MDS) system. It encapsulates all of the MDS functionality that is exposed to the user. The framework ensures that the internal functions of the product are better modularized in support of both an API and modular component development. "Services" means a modular architecture based on the Windows Communication Foundation (WCF). Master Data Services web service 15 This protocol updates the web services implementation of MDS for use with SQL Server 2016. Reporting Services The following protocols and formats are used by the Reporting Services . Format Description Reference Report Definition Language file format SQL Server Report Definition Language (RDL) is a file type that is used to represent the metadata for defining a report. Report Page Layout (RPL) binary stream format RPL is a binary format that is used by SQL Server Reporting Services when it communicates with viewer controls to offload some of the rendering work from the server to the client viewer control. By using RPL, implementers can create custom report designers that will create RPL, as well as custom report renderers that process and display RPL to display reports.
SQL Server Analysis Services 8.0 protocol This protocol provides a mechanism for a client to communicate with and perform operations on an server. This protocol is for Microsoft SQL Server 7.0 and Microsoft SQL Server 2000. This legacy protocol is superseded by . Database Engine The following protocol is used with the Database Engine. Format Description Reference SQL Server Common Language Runtime (CLR) structure This binary format consists of the GEOGRAPHY, GEOMETRY, HIERARCHYID, and structures managed by SQL Server. The structures used to transmit geography and geometry data types over the wire implement the Open Geospatial Consortium's (OGC) OpenGIS Simple Features Specification (SFS). SQL Server, therefore, provides data to a client program as text or binary representations of points, lines, polygons, and collections that conform to the specification. The hierarchyid data type enables SQL Server applications to store, retrieve, and manipulate hierarchical data.
Index A 30 11 Analysis Services ( 11, 14) 14 27 27 27 31 27 11 32 19 27 Analysis Services Reporting Protocol 14 Analysis services use cases 27 16 application development 11 32 16 21 11 14 authentication 27 28 authoring reports 26 native report portal ( 25, 26) B binary XML 11 15 11 16 C 29 CEP Engine 15 20 28 Cep engine use case 28 35 23 CLR types 15 19 29 20 20 20 15 11 30 Considerations 29 D 14 11 28 28 32 protocols ( 11, 15, 19) 28 28 Database Publishing Wizard Protocol 16 Dataset DiffGram structure 16 27 Dependencies 20 Design intent 27 28 29 14 14 E 30 20 29 examples 32 30 14 Extensibility 34 29 20 F 11 11 G 19 19 7 H 29 19 I