SQL

SQL (Template:IPAc-en,<ref name="learningSQL" /> or Template:IPAc-en;<ref name="oed" /> Structured Query Language<ref name="Britannica" /><ref name="oed-US" /><ref name="IBM-SQL" /><ref name="MS-SQL-def" />) is a special-purpose programming language designed for managing data held in a relational database management system (RDBMS), or for stream processing in a relational data stream management system (RDSMS).

Originally based upon relational algebra and tuple relational calculus, SQL consists of a data definition language, data manipulation language, and a data control language. The scope of SQL includes data insert, query, update and delete, schema creation and modification, and data access control. Although SQL is often described as, and to a great extent is, a declarative language (4GL), it also includes procedural elements.

SQL was one of the first commercial languages for Edgar F. Codd's relational model, as described in his influential 1970 paper, "A Relational Model of Data for Large Shared Data Banks."<ref name="codd-relational-model" /> Despite not entirely adhering to the relational model as described by Codd, it became the most widely used database language.<ref name="SQL-Fundamentals" /><ref name="IBM-sql" />

SQL became a standard of the American National Standards Institute (ANSI) in 1986, and of the International Organization for Standardization (ISO) in 1987.<ref name="ISO/IEC" /> Since then, the standard has been revised to include a larger set of features. Despite the existence of such standards, though, most SQL code is not completely portable among different database systems without adjustments.

History

SQL was initially developed at IBM by Donald D. Chamberlin and Raymond F. Boyce in the early 1970s.<ref name="chamberlin-boyce-sequel" /> This version, initially called SEQUEL (Structured English QUEry Language), was designed to manipulate and retrieve data stored in IBM's original quasi-relational database management system, System R, which a group at IBM San Jose Research Laboratory had developed during the 1970s.<ref name="chamberlin-boyce-sequel" /> The acronym SEQUEL was later changed to SQL because "SEQUEL" was a trademark of the UK-based Hawker Siddeley aircraft company.<ref name="oppel-databases" />

In the late 1970s, Relational Software, Inc. (now Oracle Corporation) saw the potential of the concepts described by Codd, Chamberlin, and Boyce, and developed their own SQL-based RDBMS with aspirations of selling it to the U.S. Navy, Central Intelligence Agency, and other U.S. government agencies. In June 1979, Relational Software, Inc. introduced the first commercially available implementation of SQL, Oracle V2 (Version2) for VAX computers.

After testing SQL at customer test sites to determine the usefulness and practicality of the system, IBM began developing commercial products based on their System R prototype including System/38, SQL/DS, and DB2, which were commercially available in 1979, 1981, and 1983, respectively.<ref name="IBM-history" />

Design

SQL deviates in several ways from its theoretical foundation, the relational model and its tuple calculus. In that model, a table is a set of tuples, while in SQL, tables and query results are lists of rows: the same row may occur multiple times, and the order of rows can be employed in queries (e.g. in the LIMIT clause).

Critics argue that SQL should be replaced with a language that strictly returns to the original foundation: for example, see The Third Manifesto.

Syntax

Language elements

File:SQL ANATOMY wiki.svg

A chart showing several of the SQL language elements that compose a single statement

The SQL language is subdivided into several language elements, including:

• Clauses, which are constituent components of statements and queries. (In some cases, these are optional.)<ref name="ANSI/ISO/IEC" />
• Expressions, which can produce either scalar values, or tables consisting of columns and rows of data
• Predicates, which specify conditions that can be evaluated to SQL three-valued logic (3VL) (true/false/unknown) or Boolean truth values and are used to limit the effects of statements and queries, or to change program flow.
• Queries, which retrieve the data based on specific criteria. This is an important element of SQL.
• Statements, which may have a persistent effect on schemata and data, or may control transactions, program flow, connections, sessions, or diagnostics.
  • SQL statements also include the semicolon (";") statement terminator. Though not required on every platform, it is defined as a standard part of the SQL grammar.
• Insignificant whitespace is generally ignored in SQL statements and queries, making it easier to format SQL code for readability.

Operators

Operator	Description	Example
=	Equal to	Template:Code
<>	Not equal to (many DBMSs accept != in addition to <>)	Template:Code
>	Greater than	Template:Code
<	Less than	Template:Code
>=	Greater than or equal	Template:Code
<=	Less than or equal	Template:Code
Template:Code	Between an inclusive range	Template:Code
[[Where_(SQL)#LIKE|Template:Code]]	Match a character pattern	Template:Code
Template:Code	Equal to one of multiple possible values	Template:Code
Template:Code or Template:Code	Compare to null (missing data)	Template:Code
Template:Code	Is equal to value or both are nulls (missing data)	Template:Code
Template:Code	Used to change a field name when viewing results	Template:Code

Other operators have at times been suggested and/or implemented, such as the skyline operator (for finding only those records that are not 'worse' than any others).

SQL has the case/when/then/else/end expression, which was introduced in SQL-92. In its most general form, which is called a "searched case" in the SQL standard, it works like else if in other programming languages:

<source lang="sql"> CASE WHEN n > 0

         THEN 'positive'
    WHEN n < 0
         THEN 'negative'
    ELSE 'zero'

END </source>

SQL tests WHEN conditions in the order they appear in the source. If the source does not specify an ELSE expression, SQL defaults to ELSE NULL. An abbreviated syntax—called "simple case" in the SQL standard—mirrors switch statements:

<source lang="sql"> CASE n WHEN 1

           THEN 'one'
      WHEN 2
           THEN 'two'
      ELSE 'I cannot count that high'

END </source>

This syntax uses implicit equality comparisons, with the usual caveats for comparing with NULL.

For the Oracle-SQL dialect, the latter can be shortened to an equivalent DECODE construct:

<source lang="oracle11"> SELECT DECODE(n, 1, 'one',

                2, 'two',
                   'i cannot count that high')

FROM some_table; </source>

The last value is the default; if none is specified, it also defaults to NULL. However, unlike the standard's "simple case", Oracle's DECODE considers two NULLs equal with each other.<ref name="DECODE" />

Queries

The most common operation in SQL, the query, makes use of the declarative SELECT statement. SELECT retrieves data from one or more tables, or expressions. Standard SELECT statements have no persistent effects on the database. Some non-standard implementations of SELECT can have persistent effects, such as the SELECT INTO syntax provided in some databases.<ref name="ms-sql-select-into" />

Queries allow the user to describe desired data, leaving the database management system (DBMS) to carry out planning, optimizing, and performing the physical operations necessary to produce that result as it chooses.

A query includes a list of columns to include in the final result, normally immediately following the SELECT keyword. An asterisk ("*") can be used to specify that the query should return all columns of the queried tables. SELECT is the most complex statement in SQL, with optional keywords and clauses that include:

• The FROM clause, which indicates the table(s) to retrieve data from. The FROM clause can include optional JOIN subclauses to specify the rules for joining tables.
• The WHERE clause includes a comparison predicate, which restricts the rows returned by the query. The WHERE clause eliminates all rows from the result set where the comparison predicate does not evaluate to True.
• The GROUP BY clause projects rows having common values into a smaller set of rows. GROUP BY is often used in conjunction with SQL aggregation functions or to eliminate duplicate rows from a result set. The WHERE clause is applied before the GROUP BY clause.
• The HAVING clause includes a predicate used to filter rows resulting from the GROUP BY clause. Because it acts on the results of the GROUP BY clause, aggregation functions can be used in the HAVING clause predicate.
• The ORDER BY clause identifies which column[s] to use to sort the resulting data, and in which direction to sort them (ascending or descending). Without an ORDER BY clause, the order of rows returned by an SQL query is undefined.
• The DISTINCT keyword<ref>

Template:Cite book </ref> eliminates duplicate data.<ref> Template:Cite book </ref>

The following example of a SELECT query returns a list of expensive books. The query retrieves all rows from the Book table in which the price column contains a value greater than 100.00. The result is sorted in ascending order by title. The asterisk (*) in the select list indicates that all columns of the Book table should be included in the result set.

<source lang="sql"> SELECT *

FROM  Book
WHERE price > 100.00
ORDER BY title;

</source>

The example below demonstrates a query of multiple tables, grouping, and aggregation, by returning a list of books and the number of authors associated with each book.

<source lang="sql"> SELECT Book.title AS Title,

      count(*) AS Authors
FROM  Book
JOIN  Book_author
  ON  Book.isbn = Book_author.isbn
GROUP BY Book.title;

</source>

Example output might resemble the following:

Title                  Authors
---------------------- -------
SQL Examples and Guide 4
The Joy of SQL         1
An Introduction to SQL 2
Pitfalls of SQL        1

Under the precondition that isbn is the only common column name of the two tables and that a column named title only exists in the Book table, one could re-write the query above in the following form:

<source lang="sql"> SELECT title,

      count(*) AS Authors
FROM  Book
NATURAL JOIN Book_author
GROUP BY title;

</source>

However, manyTemplate:Quantify vendors either do not support this approach, or require certain column-naming conventions for natural joins to work effectively.

SQL includes operators and functions for calculating values on stored values. SQL allows the use of expressions in the select list to project data, as in the following example, which returns a list of books that cost more than 100.00 with an additional sales_tax column containing a sales tax figure calculated at 6% of the price.

<source lang="sql"> SELECT isbn,

      title,
      price,
      price * 0.06 AS sales_tax
FROM  Book
WHERE price > 100.00
ORDER BY title;

</source>

Subqueries

Queries can be nested so that the results of one query can be used in another query via a relational operator or aggregation function. A nested query is also known as a subquery. While joins and other table operations provide computationally superior (i.e. faster) alternatives in many cases, the use of subqueries introduces a hierarchy in execution that can be useful or necessary. In the following example, the aggregation function AVG receives as input the result of a subquery:

<source lang="sql"> SELECT isbn,

      title,
      price
FROM  Book
WHERE price < (SELECT AVG(price) FROM Book)
ORDER BY title;

</source>

A subquery can use values from the outer query, in which case it is known as a correlated subquery.

Since 1999 the SQL standard allows named subqueries called common table expressions (named and designed after the IBM DB2 version 2 implementation; Oracle calls these subquery factoring). CTEs can also be recursive by referring to themselves; the resulting mechanism allows tree or graph traversals (when represented as relations), and more generally fixpoint computations.

Inline view

An Inline view is the use of referencing an SQL subquery in a FROM clause. Essentially, the inline view is a subquery that can be selected from or joined to. Inline View functionality allows the user to reference the subquery as a table. The inline view also is referred to as a derived table or a subselect. Inline view functionality was introduced in Oracle 9i.<ref name="Inline View/Derived Table" />

In the following example, the SQL statement involves a join from the initial Books table to the Inline view "Sales". This inline view captures associated book sales information using the ISBN to join to the Books table. As a result, the inline view provides the result set with additional columns (the number of items sold and the company that sold the books):

<source lang="sql"> SELECT b.isbn, b.title, b.price, sales.items_sold, sales.company_nm FROM Book b

 JOIN (SELECT SUM(Items_Sold) Items_Sold, Company_Nm, ISBN
       FROM Book_Sales
       GROUP BY Company_Nm, ISBN) sales
 ON sales.isbn = b.isbn

</source>

Null or three-valued logic (3VL)

The concept of Null was introducedTemplate:By whom into SQL to handle missing information in the relational model. The word NULL is a reserved keyword in SQL, used to identify the Null special marker. Comparisons with Null, for instance equality (=) in WHERE clauses, results in an Unknown truth value. In SELECT statements SQL returns only results for which the WHERE clause returns a value of True; i.e., it excludes results with values of False and also excludes those whose value is Unknown.

Along with True and False, the Unknown resulting from direct comparisons with Null thus brings a fragment of three-valued logic to SQL. The truth tables SQL uses for AND, OR, and NOT correspond to a common fragment of the Kleene and Lukasiewicz three-valued logic (which differ in their definition of implication, however SQL defines no such operation).<ref name="Klein" />

p AND q p True False Unknown q True Template:Yes Non-Actionable Please do not make new edits to the text.     Template:Unknown False Non-Actionable Please do not make new edits to the text.     Non-Actionable Please do not make new edits to the text.     Non-Actionable Please do not make new edits to the text.     Unknown Template:Unknown Non-Actionable Please do not make new edits to the text.     Template:Unknown p OR q p True False Unknown q True Template:Yes Template:Yes Template:Yes False Template:Yes Non-Actionable Please do not make new edits to the text.     Template:Unknown Unknown Template:Yes Template:Unknown Template:Unknown p = q p True False Unknown q True Template:Yes Non-Actionable Please do not make new edits to the text.     Template:Unknown False Non-Actionable Please do not make new edits to the text.     Template:Yes Template:Unknown Unknown Template:Unknown Template:Unknown Template:Unknown q NOT q True Non-Actionable Please do not make new edits to the text.     False Template:Yes Unknown Template:Unknown There are however disputes about the semantic interpretation of Nulls in SQL because of its treatment outside direct comparisons. As seen in the table above, direct equality comparisons between two NULLs in SQL (e.g. NULL = NULL) return a truth value of Unknown. This is in line with the interpretation that Null does not have a value (and is not a member of any data domain) but is rather a placeholder or "mark" for missing information. However, the principle that two Nulls aren't equal to each other is effectively violated in the SQL specification for the UNION and INTERSECT operators, which do identify nulls with each other.<ref name="Meyden" /> Consequently, these set operations in SQL may produce results not representing sure information, unlike operations involving explicit comparisons with NULL (e.g. those in a WHERE clause discussed above). In Codd's 1979 proposal (which was basically adopted by SQL92) this semantic inconsistency is rationalized by arguing that removal of duplicates in set operations happens "at a lower level of detail than equality testing in the evaluation of retrieval operations".<ref name="Klein" /> However, computer-science professor Ron van der Meyden concluded that "The inconsistencies in the SQL standard mean that it is not possible to ascribe any intuitive logical semantics to the treatment of nulls in SQL."<ref name="Meyden" /> Additionally, because SQL operators return Unknown when comparing anything with Null directly, SQL provides two Null-specific comparison predicates: IS NULL and IS NOT NULL test whether data is or is not Null.<ref name="SQL2003-Part2-Sec87" /> SQL does not explicitly support universal quantification, and must work it out as a negated existential quantification.<ref name="Negri" /><ref name="Fratarcangeli" /><ref name="kawash" /> There is also the "<row value expression> IS DISTINCT FROM <row value expression>" infixed comparison operator, which returns TRUE unless both operands are equal or both are NULL. Likewise, IS NOT DISTINCT FROM is defined as "NOT (<row value expression> IS DISTINCT FROM <row value expression>)". SQL:1999 also introduced BOOLEAN type variables, which according to the standard can also hold Unknown values. In practice, a number of systems (e.g. PostgreSQL) implement the BOOLEAN Unknown as a BOOLEAN NULL. Data manipulation The Data Manipulation Language (DML) is the subset of SQL used to add, update and delete data: INSERT adds rows (formally tuples) to an existing table, e.g.: <source lang="sql"> INSERT INTO example (field1, field2, field3) VALUES ('test', 'N', NULL); </source> UPDATE modifies a set of existing table rows, e.g.: <source lang="sql"> UPDATE example SET field1 = 'updated value' WHERE field2 = 'N'; </source> DELETE removes existing rows from a table, e.g.: <source lang="sql"> DELETE FROM example WHERE field2 = 'N'; </source> MERGE is used to combine the data of multiple tables. It combines the INSERT and UPDATE elements. It is defined in the SQL:2003 standard; prior to that, some databases provided similar functionality via different syntax, sometimes called "upsert". <source lang="sql"> MERGE INTO table_name USING table_reference ON (condition) WHEN MATCHED THEN UPDATE SET column1 = value1 [, column2 = value2 ...] WHEN NOT MATCHED THEN INSERT (column1 [, column2 ...]) VALUES (value1 [, value2 ...]) </source> Transaction controls Transactions, if available, wrap DML operations: START TRANSACTION (or BEGIN WORK, or BEGIN TRANSACTION, depending on SQL dialect) marks the start of a database transaction, which either completes entirely or not at all. SAVE TRANSACTION (or SAVEPOINT) saves the state of the database at the current point in transaction <source lang="sql"> CREATE TABLE tbl_1(id int); INSERT INTO tbl_1(id) VALUES(1); INSERT INTO tbl_1(id) VALUES(2); COMMIT; UPDATE tbl_1 SET id=200 WHERE id=1; SAVEPOINT id_1upd; UPDATE tbl_1 SET id=1000 WHERE id=2; ROLLBACK to id_1upd; SELECT id from tbl_1; </source> COMMIT makes all data changes in a transaction permanent. ROLLBACK discards all data changes since the last COMMIT or ROLLBACK, leaving the data as it was prior to those changes. Once the COMMIT statement completes, the transaction's changes cannot be rolled back. COMMIT and ROLLBACK terminate the current transaction and release data locks. In the absence of a START TRANSACTION or similar statement, the semantics of SQL are implementation-dependent. The following example shows a classic transfer of funds transaction, where money is removed from one account and added to another. If either the removal or the addition fails, the entire transaction is rolled back. <source lang="sql"> START TRANSACTION; UPDATE Account SET amount=amount-200 WHERE account_number=1234; UPDATE Account SET amount=amount+200 WHERE account_number=2345; IF ERRORS=0 COMMIT; IF ERRORS<>0 ROLLBACK; </source> Data definition The Data Definition Language (DDL) manages table and index structure. The most basic items of DDL are the CREATE, ALTER, RENAME, DROP and TRUNCATE statements: CREATE creates an object (a table, for example) in the database, e.g.: <source lang="sql"> CREATE TABLE example( column1 INTEGER, column2 VARCHAR(50), column3 DATE NOT NULL, PRIMARY KEY (column1, column2) ); </source> ALTER modifies the structure of an existing object in various ways, for example, adding a column to an existing table or a constraint, e.g.: <source lang="sql"> ALTER TABLE example ADD column4 NUMBER(3) NOT NULL; </source> TRUNCATE deletes all data from a table in a very fast way, deleting the data inside the table and not the table itself. It usually implies a subsequent COMMIT operation, i.e., it cannot be rolled back (data is not written to the logs for rollback later, unlike DELETE). <source lang="sql"> TRUNCATE TABLE example; </source> DROP deletes an object in the database, usually irretrievably, i.e., it cannot be rolled back, e.g.: <source lang="sql"> DROP TABLE example; </source> Data types Each column in an SQL table declares the type(s) that column may contain. ANSI SQL includes the following data types.<ref name="SQL1992" /> Character strings CHARACTER(n) or CHAR(n): fixed-width n-character string, padded with spaces as needed CHARACTER VARYING(n) or VARCHAR(n): variable-width string with a maximum size of n characters NATIONAL CHARACTER(n) or NCHAR(n): fixed width string supporting an international character set NATIONAL CHARACTER VARYING(n) or NVARCHAR(n): variable-width NCHAR string Bit strings BIT(n): an array of n bits BIT VARYING(n): an array of up to n bits Numbers INTEGER, SMALLINT and BIGINT FLOAT, REAL and DOUBLE PRECISION NUMERIC(precision, scale) or DECIMAL(precision, scale) For example, the number 123.45 has a precision of 5 and a scale of 2. The precision is a positive integer that determines the number of significant digits in a particular radix (binary or decimal). The scale is a non-negative integer. A scale of 0 indicates that the number is an integer. For a decimal number with scale S, the exact numeric value is the integer value of the significant digits divided by 10S. SQL provides a function to round numerics or dates, called TRUNC (in Informix, DB2, PostgreSQL, Oracle and MySQL) or ROUND (in Informix, SQLite, Sybase, Oracle, PostgreSQL and Microsoft SQL Server)<ref name="Jones 127" /> Temporal (date/time) DATE: for date values (e.g. 2011-05-03) TIME: for time values (e.g. 15:51:36). The granularity of the time value is usually a tick (100 nanoseconds). TIME WITH TIME ZONE or TIMETZ: the same as TIME, but including details about the time zone in question. TIMESTAMP: This is a DATE and a TIME put together in one variable (e.g. 2011-05-03 15:51:36). TIMESTAMP WITH TIME ZONE or TIMESTAMPTZ: the same as TIMESTAMP, but including details about the time zone in question. SQL provides several functions for generating a date / time variable out of a date / time string (TO_DATE, TO_TIME, TO_TIMESTAMP), as well as for extracting the respective members (seconds, for instance) of such variables. The current system date / time of the database server can be called by using functions like NOW. The IBM Informix implementation provides the EXTEND and the FRACTION functions to increase the accuracy of time, for systems requiring sub-second precision.<ref name="sqlr150" /> Data control The Data Control Language (DCL) authorizes users to access and manipulate data. Its two main statements are: GRANT authorizes one or more users to perform an operation or a set of operations on an object. REVOKE eliminates a grant, which may be the default grant. Example: <source lang="sql"> GRANT SELECT, UPDATE ON example TO some_user, another_user; REVOKE SELECT, UPDATE ON example FROM some_user, another_user; </source> Procedural extensions SQL is designed for a specific purpose: to query data contained in a relational database. SQL is a set-based, declarative programming language, not an imperative programming language like C or BASIC. However, extensions to Standard SQL add procedural programming language functionality, such as control-of-flow constructs. These include: Source Common name Full name ANSI/ISO Standard SQL/PSM SQL/Persistent Stored Modules Interbase / Firebird PSQL Procedural SQL IBM DB2 SQL PL SQL Procedural Language (implements SQL/PSM) IBM Informix SPL Stored Procedural Language IBM Netezza NZPLSQL [1] (based on Postgres PL/pgSQL) Microsoft / Sybase T-SQL Transact-SQL Mimer SQL SQL/PSM SQL/Persistent Stored Module (implements SQL/PSM) MySQL SQL/PSM SQL/Persistent Stored Module (implements SQL/PSM) MonetDB SQL/PSM SQL/Persistent Stored Module (implements SQL/PSM) NuoDB SSP Starkey Stored Procedures Oracle PL/SQL Procedural Language/SQL (based on Ada) PostgreSQL PL/pgSQL Procedural Language/PostgreSQL Structured Query Language (implements SQL/PSM) Sybase Watcom-SQL SQL Anywhere Watcom-SQL Dialect Teradata SPL Stored Procedural Language SAP SAP HANA SQL Script In addition to the standard SQL/PSM extensions and proprietary SQL extensions, procedural and object-oriented programmability is available on many SQL platforms via DBMS integration with other languages. The SQL standard defines SQL/JRT extensions (SQL Routines and Types for the Java Programming Language) to support Java code in SQL databases. SQL Server 2005 uses the SQLCLR (SQL Server Common Language Runtime) to host managed .NET assemblies in the database, while prior versions of SQL Server were restricted to unmanaged extended stored procedures primarily written in C. PostgreSQL lets users write functions in a wide variety of languages—including Perl, Python, Tcl, and C.<ref name="PostgreSQL server programming" /> Interoperability and standardization SQL implementations are incompatible between vendors and do not necessarily completely follow standards. In particular date and time syntax, string concatenation, NULLs, and comparison case sensitivity vary from vendor to vendor. A particular exception is PostgreSQL, which strives for standards compliance.<ref name="About PostgreSQL" /> Popular implementations of SQL commonly omit support for basic features of Standard SQL, such as the DATE or TIME data types. The most obvious such examples, and incidentally the most popular commercial and proprietary SQL DBMSs, are Oracle (whose DATE behaves as DATETIME,<ref name="Ora DATE" /><ref name="Ora DATETIME" /> and lacks a TIME type)<ref name="Ora TIME" /> and MS SQL Server (before the 2008 version). As a result, SQL code can rarely be ported between database systems without modifications. There are several reasons for this lack of portability between database systems: The complexity and size of the SQL standard means that most implementors do not support the entire standard. The standard does not specify database behavior in several important areas (e.g. indexes, file storage...), leaving implementations to decide how to behave. The SQL standard precisely specifies the syntax that a conforming database system must implement. However, the standard's specification of the semantics of language constructs is less well-defined, leading to ambiguity. Many database vendors have large existing customer bases; where the newer version of the SQL standard conflicts with the prior behavior of the vendor's database, the vendor may be unwilling to break backward compatibility. There is little commercial incentive for vendors to make it easier for users to change database suppliers (see vendor lock-in). Users evaluating database software tend to place other factors such as performance higher in their priorities than standards conformance. SQL was adopted as a standard by the American National Standards Institute (ANSI) in 1986 as SQL-86<ref name="X3H2" /> and the International Organization for Standardization (ISO) in 1987. Nowadays the standard is subject to continuous improvement by the Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 32, Data management and interchange, which affiliate to ISO as well as IEC. It is commonly denoted by the pattern: ISO/IEC 9075-n:yyyy Part n: title, or, as a shortcut, ISO/IEC 9075. ISO/IEC 9075 is complemented by ISO/IEC 13249: SQL Multimedia and Application Packages (SQL/MM), which defines SQL based interfaces and packages to widely spread applications like video, audio and spatial data. Until 1996, the National Institute of Standards and Technology (NIST) data management standards program certified SQL DBMS compliance with the SQL standard. Vendors now self-certify the compliance of their products.<ref name="Doll" /> The original standard declared that the official pronunciation for "SQL" was an initialism: Template:IPAc-en ("es queue el").<ref name="SQL-Fundamentals" /> Regardless, many English-speaking database professionals (including Donald Chamberlin himself<ref name="Gillespie" />) use the acronym-like pronunciation of Template:IPAc-en ("sequel"),<ref name="Melton" /> mirroring the language's pre-release development name of "SEQUEL".<ref name=chamberlin-boyce-sequel /><ref name=oppel-databases /> The SQL standard has gone through a number of revisions: Year Name Alias Comments 1986 SQL-86 SQL-87 First formalized by ANSI. 1989 SQL-89 FIPS 127-1 Minor revision that added integrity constraints, adopted as FIPS 127-1. 1992 SQL-92 SQL2, FIPS 127-2 Major revision (ISO 9075), Entry Level SQL-92 adopted as FIPS 127-2. 1999 SQL:1999 SQL3 Added regular expression matching, recursive queries (e.g. transitive closure), triggers, support for procedural and control-of-flow statements, non-scalar types, and some object-oriented features (e.g. structured types). Support for embedding SQL in Java (SQL/OLB) and vice versa (SQL/JRT). 2003 SQL:2003 SQL 2003 Introduced XML-related features (SQL/XML), window functions, standardized sequences, and columns with auto-generated values (including identity-columns). 2006 SQL:2006 SQL 2006 ISO/IEC 9075-14:2006 defines ways that SQL can be used with XML. It defines ways of importing and storing XML data in an SQL database, manipulating it within the database, and publishing both XML and conventional SQL-data in XML form. In addition, it lets applications integrate queries into their SQL code with XQuery, the XML Query Language published by the World Wide Web Consortium (W3C), to concurrently access ordinary SQL-data and XML documents.<ref name="SQLXML2006" /> 2008 SQL:2008 SQL 2008 Legalizes ORDER BY outside cursor definitions. Adds INSTEAD OF triggers. Adds the TRUNCATE statement.<ref name="iablog.sybase.com-paulley" /> 2011 SQL:2011 Interested parties may purchase SQL standards documents from ISO,<ref name="ISO/IEC 9075-2:2011" /> IEC or ANSI. A draft of SQL:2008 is freely available as a zip archive.<ref name="Whitemarsh" /> The SQL standard is divided into nine parts. ISO/IEC 9075-1:2011 Part 1: Framework (SQL/Framework). It provides logical concepts. ISO/IEC 9075-2:2011 Part 2: Foundation (SQL/Foundation). It contains the most central elements of the language and consists of both mandatory and optional features. ISO/IEC 9075-3:2008 Part 3: Call-Level Interface (SQL/CLI). It defines interfacing components (structures, procedures, variable bindings) that can be used to execute SQL statements from applications written in Ada, C respectively C++, COBOL, Fortran, MUMPS, Pascal or PL/I. (For Java see part 10.) SQL/CLI is defined in such a way that SQL statements and SQL/CLI procedure calls are treated as separate from the calling application's source code. Open Database Connectivity is a well-known superset of SQL/CLI. This part of the standard consists solely of mandatory features. ISO/IEC 9075-4:2011 Part 4: Persistent Stored Modules (SQL/PSM) It standardizes procedural extensions for SQL, including flow of control, condition handling, statement condition signals and resignals, cursors and local variables, and assignment of expressions to variables and parameters. In addition, SQL/PSM formalizes declaration and maintenance of persistent database language routines (e.g., "stored procedures"). This part of the standard consists solely of optional features. ISO/IEC 9075-9:2008 Part 9: Management of External Data (SQL/MED). It provides extensions to SQL that define foreign-data wrappers and datalink types to allow SQL to manage external data. External data is data that is accessible to, but not managed by, an SQL-based DBMS. This part of the standard consists solely of optional features. ISO/IEC 9075-10:2008 Part 10: Object Language Bindings (SQL/OLB). It defines the syntax and semantics of SQLJ, which is SQL embedded in Java (see also part 3). The standard also describes mechanisms to ensure binary portability of SQLJ applications, and specifies various Java packages and their contained classes. This part of the standard consists solely of optional features, as opposed to SQL/OLB JDBC, which is not part of the SQL standard, which defines an API.Template:Citation needed ISO/IEC 9075-11:2011 Part 11: Information and Definition Schemas (SQL/Schemata). It defines the Information Schema and Definition Schema, providing a common set of tools to make SQL databases and objects self-describing. These tools include the SQL object identifier, structure and integrity constraints, security and authorization specifications, features and packages of ISO/IEC 9075, support of features provided by SQL-based DBMS implementations, SQL-based DBMS implementation information and sizing items, and the values supported by the DBMS implementations.<ref name="ISO/IEC 9075-11:2008" /> This part of the standard contains both mandatory and optional features. ISO/IEC 9075-13:2008 Part 13: SQL Routines and Types Using the Java Programming Language (SQL/JRT). It specifies the ability to invoke static Java methods as routines from within SQL applications ('Java-in-the-database'). It also calls for the ability to use Java classes as SQL structured user-defined types. This part of the standard consists solely of optional features. ISO/IEC 9075-14:2011 Part 14: XML-Related Specifications (SQL/XML). It specifies SQL-based extensions for using XML in conjunction with SQL. The XML data type is introduced, as well as several routines, functions, and XML-to-SQL data type mappings to support manipulation and storage of XML in an SQL database.<ref name="SQLXML2006" /> This part of the standard consists solely of optional features.Template:Citation needed ISO/IEC 9075 is complemented by ISO/IEC 13249 SQL Multimedia and Application Packages. This closely related but separate standard is developed by the same committee. It defines interfaces and packages based on SQL. The aim is a unified access to typical database applications like text, pictures, data mining or spatial data. ISO/IEC 13249-1:2007 Part 1: Framework ISO/IEC 13249-2:2003 Part 2: Full-Text ISO/IEC 13249-3:2011 Part 3: Spatial ISO/IEC 13249-5:2003 Part 5: Still image ISO/IEC 13249-6:2006 Part 6: Data mining ISO/IEC 13249-8:xxxx Part 8: Metadata registries (MDR) (work in progress) Alternatives A distinction should be made between alternatives to SQL as a language, and alternatives to the relational model itself. Below are proposed relational alternatives to the SQL language. See navigational database and NoSQL for alternatives to the relational model. .QL: object-oriented Datalog 4D Query Language (4D QL) BQL: a superset that compiles down to SQL Datalog: critics suggest that Datalog has two advantages over SQL: it has cleaner semantics, which facilitates program understanding and maintenance, and it is more expressive, in particular for recursive queries.<ref name="PROLE" /> HTSQL: URL based query method IBM Business System 12 (IBM BS12): one of the first fully relational database management systems, introduced in 1982 ISBL jOOQ: SQL implemented in Java as an internal domain-specific language Java Persistence Query Language (JPQL): The query language used by the Java Persistence API and Hibernate persistence library LINQ: Runs SQL statements written like language constructs to query collections directly from inside .Net code. Object Query Language QBE (Query By Example) created by Moshè Zloof, IBM 1977 Quel introduced in 1974 by the U.C. Berkeley Ingres project. Tutorial D XQuery Distributed SQL processing Distributed Relational Database Architecture (DRDA) was designed by a work group within IBM in the period 1988 to 1994. DRDA enables network connected relational databases to cooperate to fulfill SQL requests.<ref>Template:Cite journal</ref><ref>Template:Cite book</ref> An interactive user or program can issue SQL statements to a local RDB and receive tables of data and status indicators in reply from remote RDBs. SQL statements can also be compiled and stored in remote RDBs as packages and then invoked by package name. This is important for the efficient operation of application programs that issue complex, high-frequency queries. It is especially important when the tables to be accessed are located in remote systems. The messages, protocols, and structural components of DRDA are defined by the Distributed Data Management Architecture. See also Comparison of object-relational database management systems Comparison of relational database management systems D (data language specification) D4 (programming language) Hierarchical model List of relational database management systems MUMPS NoSQL Transact-SQL Online analytical processing (OLAP) Online transaction processing (OLTP) Data warehouse relational data stream management system Star schema Snowflake schema DB2 SQL return codes Notes references-column-width references-column-count references-column-count-{{#if:1|30em}} }} {{#if: references-column-width }} }}" style="{{#if: 30em {{#iferror: {{#ifexpr: 30em > 1 }} Template:Column-width Template:Column-count }} {{#if: Template:Column-width }} }} list-style-type: {{#switch: upper-alpha upper-roman lower-alpha lower-greek lower-roman = {{{group}}} #default = decimal}};"> <references group=""><ref name="ars">Template:Cite web</ref> <ref name="iana">Template:Cite web</ref> <ref name="application/sql">Template:Cite web</ref> <ref name="learningSQL">Template:Cite book</ref> <ref name="oed">Template:Cite web</ref> <ref name="Britannica">Template:Cite web</ref> <ref name="oed-US">Template:Cite web </ref> <ref name="IBM-SQL">Template:Cite web</ref> <ref name="MS-SQL-def">Template:Cite web</ref> <ref name="codd-relational-model">Template:Cite journal</ref> <ref name="SQL-Fundamentals">Template:Cite web</ref> <ref name="IBM-sql">Template:Cite web</ref> <ref name="ISO/IEC">Template:Cite web</ref> <ref name="chamberlin-boyce-sequel">Template:Cite journal</ref> <ref name="oppel-databases">Template:Cite book</ref> <ref name="IBM-history">Template:Cite web</ref> <ref name="ANSI/ISO/IEC">ANSI/ISO/IEC International Standard (IS). Database Language SQL—Part 2: Foundation (SQL/Foundation). 1999.</ref> <ref name="DECODE">Template:Cite web</ref> <ref name="ms-sql-select-into">Template:Cite book</ref> <ref name="Inline View/Derived Table">Template:Cite web</ref> <ref name="Klein">Template:Cite book</ref> <ref name="Meyden">Ron van der Meyden, "Logical approaches to incomplete information: a survey" in Chomicki, Jan; Saake, Gunter (Eds.) Logics for Databases and Information Systems, Kluwer Academic Publishers ISBN 978-0-7923-8129-7, p. 344</ref> <ref name="SQL2003-Part2-Sec87">Template:Cite book</ref> <ref name="Negri">M. Negri, G. Pelagatti, L. Sbattella (1989) GUIDE Semantics and problems of universal quantification in SQL</ref> <ref name="Fratarcangeli">Fratarcangeli, Claudio (1991). Technique for universal quantification in SQL. ACM.org.</ref> <ref name="kawash">Kawash, Jalal (2004) Complex quantification in Structured Query Language (SQL): a tutorial using relational calculus - Journal of Computers in Mathematics and Science Teaching ISSN 0731-9258 Volume 23, Issue 2, 2004 AACE Norfolk, Virginia. Thefreelibrary.com</ref> <ref name="SQL1992">Template:Cite journal (proposed revised text of DIS 9075).</ref> <ref name="Jones 127">Arie Jones, Ryan K. Stephens, Ronald R. Plew, Alex Kriegel, Robert F. Garrett (2005), SQL Functions Programmer's Reference. Wiley, 127 pages.</ref> <ref name="sqlr150">[2]</ref> <ref name="PostgreSQL server programming">Template:Cite web</ref> <ref name="PROLE">[3]</ref> <ref name="About PostgreSQL">Template:Cite web</ref> <ref name="Ora DATE">Template:Cite book</ref> <ref name="Ora DATETIME">Template:Cite book</ref> <ref name="Ora TIME">Template:Cite book</ref> <ref name="X3H2">Template:Cite book</ref> <ref name="Doll">Template:Cite web</ref> <ref name="Gillespie">Template:Cite web</ref> <ref name="Melton">Template:Cite book</ref> <ref name="SQLXML2006">Template:Cite book</ref> <ref name="iablog.sybase.com-paulley">Template:Cite journal</ref> <ref name="ISO/IEC 9075-2:2011">Template:Cite web</ref> <ref name="Whitemarsh">Template:Cite journal</ref> <ref name="ISO/IEC 9075-11:2008">Template:Cite journal</ref></references> References Template:Cite journal Discussion on alleged SQL flaws (C2 wiki) C. J. Date with Hugh Darwen: A Guide to the SQL standard : a users guide to the standard database language SQL, 4th ed., Addison Wesley, USA 1997, ISBN 978-0-201-96426-4 External links 1995 SQL Reunion: People, Projects, and Politics, by Paul McJones (ed.): transcript of a reunion meeting devoted to the personal history of relational databases and SQL. American National Standards Institute. X3H2 Records, 1978–1995 Charles Babbage Institute Collection documents the H2 committee's development of the NDL and SQL standards. Oral history interview with Donald D. Chamberlin Charles Babbage Institute In this oral history Chamberlin recounts his early life, his education at Harvey Mudd College and Stanford University, and his work on relational database technology. Chamberlin was a member of the System R research team and, with Raymond F. Boyce, developed the SQL database language. Chamberlin also briefly discusses his more recent research on XML query languages. Comparison of Different SQL Implementations This comparison of various SQL implementations is intended to serve as a guide to those interested in porting SQL code between various RDBMS products, and includes comparisons between SQL:2008, PostgreSQL, DB2, MS SQL Server, MySQL, Oracle, and Informix. Event stream processing with SQL - An introduction to real-time processing of streaming data with continuous SQL queries