Skip to content

transact-sql-reference-database-engine.md

Latest commit

 

History

History
74 lines (50 loc) · 5.32 KB

transact-sql-reference-database-engine.md

File metadata and controls

74 lines (50 loc) · 5.32 KB
title Transact-SQL Reference (Database Engine) | Microsoft Docs
ms.custom
ms.date 03/15/2017
ms.prod sql-non-specified
ms.reviewer
ms.suite
ms.technology
database-engine
ms.tgt_pltfrm
ms.topic language-reference
f1_keywords
sql13.tsqlref.f1
devlang-tsql
helpviewer_keywords
Transact-SQL
ms.assetid dbba47d7-e08e-4435-b876-35dced1f325d
caps.latest.revision 14
author BYHAM
ms.author rickbyh
manager jhubbard

Transact-SQL Reference (Database Engine)

[!INCLUDEtsql-appliesto-ss2008-all_md]

[!INCLUDEtsql] is central to using [!INCLUDEssNoVersion]. All applications that communicate with an instance of [!INCLUDEssNoVersion] do so by sending [!INCLUDEtsql] statements to the server, regardless of the user interface of the application.

The following is a list of the kinds of applications that can generate [!INCLUDEtsql]:

  • General office productivity applications.

  • Applications that use a graphical user interface (GUI) to let users select the tables and columns from which they want to see data.

  • Applications that use general language sentences to determine what data a user wants to see.

  • Line of business applications that store their data in [!INCLUDEssNoVersion] databases. These applications can include both applications written by vendors and applications written in-house.

  • [!INCLUDEtsql] scripts that are run by using utilities such as sqlcmd.

  • Applications created by using development systems such as [!INCLUDEmsCoName] [!INCLUDEvcprvc], [!INCLUDEmsCoName] [!INCLUDEvbprvb], or [!INCLUDEmsCoName] Visual J++ that use database APIs such as ADO, OLE DB, and ODBC.

  • Web pages that extract data from [!INCLUDEssNoVersion] databases.

  • Distributed database systems from which data from [!INCLUDEssNoVersion] is replicated to various databases, or distributed queries are executed.

  • Data warehouses in which data is extracted from online transaction processing (OLTP) systems and summarized for decision-support analysis.

To view the Transact-SQL reference topics

To view the list of topics in the [!INCLUDEtsql] reference section of SQL Server Books Online, follow these steps:

  1. On the SQL Server Books Online toolbar, click the Sync with Table Of Contents button.

  2. On the Contents tab, expand [!INCLUDEtsql] Reference.

Note

When viewing this content in the MSDN Library, use the Table of Contents to browse for topics or search for commands by name.

For a list of [!INCLUDEtsql] functions by category, see Functions.

For a short tutorial about how to write [!INCLUDEtsql], see Tutorial: Writing Transact-SQL Statements.

For help with [!INCLUDEtsql] statements, see MSDN Transact-SQL Forum.

"Applies to" References

The [!INCLUDEtsql] reference includes topics related to [!INCLUDEssKatmai], [!INCLUDEssKilimanjaro], [!INCLUDEssSQL11], [!INCLUDEssSQL14], and [!INCLUDEssSDSfull]. Near the top of each topic is a section indicating which products support the subject of the topic. If a product is omitted, then the feature described by the topic is not available in that product. For example, availability groups were introduced in [!INCLUDEssSQL11]. The CREATE AVAILABILTY GROUP topic indicates it applies to SQL Server (SQL Server 2012 through current version) because it does not apply to [!INCLUDEssKatmai], [!INCLUDEssKilimanjaro], or [!INCLUDEssSDSfull].

In some cases, the general subject of topic can be used in a product, but all of the arguments are not supported. For example, contained database users were introduced in [!INCLUDEssSQL11]. The CREATE USER statement can be used in any [!INCLUDEssNoVersion] product, however the WITH PASSWORD syntax cannot be used with older versions. In this case, additional Applies to sections are inserted into the appropriate argument descriptions in the body of the topic.

See Also

Transact-SQL Syntax Conventions (Transact-SQL)
SQL Server Database Engine