Preview Documents

This topic lists the available preview, or pre-release, documents. Since this topic is updated frequently, we recommend that you subscribe to the RSS or Atom feed to receive update notifications.

RSS

Atom

The Microsoft SQL Server Protocols documentation contains detailed technical specifications for Microsoft protocols that are implemented and used by SQL Server to interoperate or communicate with other Microsoft products. It also contains technical specifications for extensions to industry-standard and other published protocols that are used by SQL Server. In addition, the documentation set includes a companion overview document that supplements the technical specifications with conceptual background information, overviews of inter-protocol relationships and interactions, and technical references.

Documentation for released versions of SQL Server is at SQL Server Protocols.

New Preview Documentation

The following SQL Server Protocols document has not yet been released at SQL Server Protocols.

Specification

Description

Preview date

[MS-CPREST-Preview]: Control Plane REST API

Specifies the Control Plane REST API protocol, which is an HTTP-based web service API that deploys data services and applications into a managed cluster environment. This protocol then uses management service APIs to manage high-value data stored in relational databases that have been integrated with high-volume data resources within the dedicated cluster.

April 2019

Updated Preview Documentation

The following SQL Server Protocols documents were previously released and have been updated. These documents contain revision marks that show changes due to support for Microsoft SQL Server 2019 Community Technology Previews (CTPs) and document updates made since the documents were last released at SQL Server Protocols. A Preview document, provided in PDF format, shows additions in red, underlined text and deletions in red, strikethrough text.

Specification

Description

Preview date

[MS-ODBCSTR-Diff]: ODBC Connection String Structure

Specifies the format of the connection string used in Open Database Connectivity (ODBC).

This document has been updated to add a description of the new client-certificate authentication feature that provides users with an alternative to username-and-password authentication.

May 2019

[MS-SCCSTR-Diff]: SqlClient Connection String Structure

Specifies a method for Microsoft .NET Framework applications to specify the parameters to connect to a data source that enables developers to query, update, insert, and delete data on SQL Server.

This document has been updated to include information about enhanced confidentiality and security through column encryption and enclave technologies.

March 2019

[MS-SSAS-Diff]: SQL Server Analysis Services Protocol

Specifies the methods for a client to communicate with and to perform operations on an analysis server.

This document has been updated to specify the new DbpropMsmdRequestMemoryLimit and Memory\QueryMemoryLimit properties, which control the amount of memory that can be used during a query.

March 2019

[MS-SSAS-T-Diff]: SQL Server Analysis Services Tabular Protocol

Specifies an extension of the SQL Server Analysis Services protocol [MS-SSAS] by specifying the methods for a client to communicate with and perform operations on an analysis server that uses Tabular databases that are at compatibility level 1200 or higher.

This document has been updated to specify the new CalculationGroup feature that enables calculation of a value based on an expression. Calculation groups address a common issue in complex models where there can be a proliferation of measures that use the same calculations. This feature requires models to be at compatibility level 1470 or higher.

The document has also been updated to specify the ForceUniqueNames property of the Model object, the DataCategory property of the Measure object, and the ContentType property of the LinguisticMetadata object. The DataCategory property requires models to be at compatibility level 1455 or higher, and the ForceUniqueNames and ContentType properties require models to be at compatibility level 1465 or higher.

May 2019