SQL Server Language Reference
Applies To: SQL Server 2014, SQL Server 2016 Preview
Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2).
Microsoft SQL Server Language Reference contains language reference content for the following areas.
The Transact-SQL topics in this SQL Server Language Reference node have been modified to include the following information.
The versions of SQL Server (starting with SQL Server 2008) that apply to each topic.
The Microsoft platforms (SQL Server and Azure SQL Database) that apply to each topic.
By using this information you can easily identify the Transact-SQL statements, commands, and system objects that apply to the versions and platforms for which you develop applications or administer and support. In addition, the consolidated topics provide a single "master" content set that will be maintained for all of the specified versions and platforms. That is, you can rely on this single content set for the most accurate and up-to-date product information regardless of version or platform.
Identifying Version and Platform Applicability
Version and platform applicability is provided in the top section of each topic in a single "applies to" statement. This statement identifies the applicable versions and platforms for the topic as a whole. The following examples demonstrate this statement.
Example A. The following statement indicates that the contents of the topic apply to the SQL Server 2008 through SQL Server 2016 and to both the SQL Server and Azure SQL Database platforms.
Applies to: SQL Server (SQL Server 2008 through current version), Azure SQL Database.
Example B. The following statement indicates that the contents of the topic apply to the SQL Server versions SQL Server 2012 through SQL Server 2016 and to only the SQL Server platform.
Applies to: SQL Server (SQL Server 2012 through current version).
Identifying Version and Platform Exceptions
For most of the Transact-SQL topics, the top-level "applies to" statement is all that is required to identify version and platform applicability. However, some statements and system objects have changed over time to support new features in the product. These additions do not apply to the older versions. For example, the statement ORDER BY Clause applies to all SQL Server versions and to SQL Database, but a new OFFSET…FETCH argument was added in SQL Server 2012 that applies only to that version and higher versions and to SQL Database. Such exceptions to the top-level applies to statement are identified in the Arguments section of the topic in the definition of the new syntax. For example, in the ORDE BY topic, the following statement is added to the definitions of OFFSET and FETCH. This statement indicates that these keywords cannot be used in versions of SQL Server earlier than SQL Server 2012.
Applies to: SQL Server 2012 through SQL Server 2016 and Azure SQL Database.
Exceptions to the top-level applies to statement can also occur when the topic is applicable to both the SQL Server and Azure SQL Database but only some of the syntax is supported by Azure SQL Database. For example, the DROP INDEX statement applies to both platforms, however, Azure SQL Database does not support all of the options and clauses that SQL Server provides. These exceptions are identified in the Arguments section. For example, in the definition of MAXDOP, the following statement is added to specify the versions and platforms that can specify this option.
Applies to: SQL Server 2008 through SQL Server 2016.
Exceptions to the top-level applies to statement can also occur in system objects such as catalog views. For these objects, new columns can be added or new values returned by existing columns. When a new column is added, the version/platform applicability is included in the definition of the column. When new values are returned by an existing column, the applicability of the new values are identified in the description of the values. For example, the values returned in the type column of the sys.indexes catalog view have changed from release to release. In the definition of that column, the applicability of the values are defined for each value that does not conform to the top-level "applies to" statement.