|Designed by||Donald D. Chamberlin|
Raymond F. Boyce
|Developer||ISO/IEC JTC 1 (Joint Technical Committee 1) / SC 32 (Subcommittee 32) / WG 3 (Working Group 3)|
SQL:2016 / December 2016
|Typing discipline||Static, strong|
|CQL, LINQ, SPARQL, SOQL, PowerShell, JPQL, jOOQ, N1QL|
|Internet media type|
|Type of format||Database|
SQL (/ /(listen) S-Q-L, // "sequel"; Structured Query Language) is a domain-specific language used in programming and designed for managing data held in a relational database management system (RDBMS), or for stream processing in a relational data stream management system (RDSMS). It is particularly useful in handling structured data, i.e. data incorporating relations among entities and variables.
SQL offers two main advantages over older read–write APIs such as ISAM or VSAM. Firstly, it introduced the concept of accessing many records with one single command. Secondly, it eliminates the need to specify how to reach a record, e.g. with or without an index.
Originally based upon relational algebra and tuple relational calculus, SQL consists of many types of statements, which may be informally classed as sublanguages, commonly: a data query language (DQL),[a] a data definition language (DDL),[b] a data control language (DCL), and a data manipulation language (DML).[c] The scope of SQL includes data query, data manipulation (insert, update and delete), data definition (schema creation and modification), and data access control. Although SQL is essentially a declarative language (4GL), it also includes procedural elements.
SQL was one of the first commercial languages to use Edgar F. Codd’s relational model. The model was described in his influential 1970 paper, "A Relational Model of Data for Large Shared Data Banks". Despite not entirely adhering to the relational model as described by Codd, it became the most widely used database language.
SQL became a standard of the American National Standards Institute (ANSI) in 1986 and of the International Organization for Standardization (ISO) in 1987. Since then, the standard has been revised to include a larger set of features. Despite the existence of standards, most SQL code requires at least some changes before being ported to different database systems.
SQL was initially developed at IBM by Donald D. Chamberlin and Raymond F. Boyce after learning about the relational model from Edgar F. Codd in the early 1970s. This version, initially called SEQUEL (Structured English Query Language), was designed to manipulate and retrieve data stored in IBM's original quasirelational database management system, System R, which a group at IBM San Jose Research Laboratory had developed during the 1970s.
Chamberlin and Boyce's first attempt at a relational database language was SQUARE (Specifying Queries in A Relational Environment), but it was difficult to use due to subscript/superscript notation. After moving to the San Jose Research Laboratory in 1973, they began work on a sequel to SQUARE. The name SEQUEL was later changed to SQL (dropping the vowels) because "SEQUEL" was a trademark of the UK-based Hawker Siddeley Dynamics Engineering Limited company. The label SQL later became the acronym for Structured Query Language.
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 IBM Db2, which were commercially available in 1979, 1981, and 1983, respectively.
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 introduced one of the first commercially available implementations of SQL, Oracle V2 (Version2) for VAX computers.
By 1986, ANSI and ISO standard groups officially adopted the standard "Database Language SQL" language definition. New versions of the standard were published in 1989, 1992, 1996, 1999, 2003, 2006, 2008, 2011, and most recently, 2016.
Main article: SQL syntax
The SQL language is subdivided into several language elements, including:
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:
|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||(based on Postgres PL/pgSQL)|
|Invantive||PSQL||Invantive Procedural SQL (implements SQL/PSM and PL/SQL)|
|MariaDB||SQL/PSM, PL/SQL||SQL/Persistent Stored Module (implements SQL/PSM), Procedural Language/SQL (based on Ada)|
|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 (based on reduced PL/SQL)|
|SAP R/3||ABAP||Advanced Business Application Programming|
|Sybase||Watcom-SQL||SQL Anywhere Watcom-SQL Dialect|
|Teradata||SPL||Stored Procedural Language|
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. Particular exceptions are PostgreSQL and Mimer SQL which strive for standards compliance, though PostgreSQL does not adhere to the standard in all cases. For example, the folding of unquoted names to lower case in PostgreSQL is incompatible with the SQL standard, which says that unquoted names should be folded to upper case. Thus,
Foo should be equivalent to
foo according to the standard.
Popular implementations of SQL commonly omit support for basic features of Standard SQL, such as the
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, and lacks a
TIME type) and MS SQL Server (before the 2008 version). As a result, SQL code can rarely be ported between database systems without modifications.
Several reasons for this lack of portability between database systems include:
SQL was adopted as a standard by the ANSI in 1986 as SQL-86 and the ISO in 1987. It is maintained by ISO/IEC JTC 1, Information technology, Subcommittee SC 32, Data management and interchange.
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.
The original standard declared that the official pronunciation for "SQL" was an initialism: // ("ess cue el"). Regardless, many English-speaking database professionals (including Donald Chamberlin himself) use the acronym-like pronunciation of // ("sequel"), mirroring the language's prerelease development name, "SEQUEL".
The SQL standard has gone through a number of revisions:
|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, nonscalar types (arrays), 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||Introduced XML-related features (SQL/XML), window functions, standardized sequences, and columns with autogenerated values (including identity columns)|
|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.|
|2008||SQL:2008||Legalizes ORDER BY outside cursor definitions. Adds INSTEAD OF triggers, TRUNCATE statement, FETCH clause|
|2011||SQL:2011||Adds temporal data (PERIOD FOR) (more information at Temporal database#History). Enhancements for window functions and FETCH clause.|
|2016||SQL:2016||Adds row pattern matching, polymorphic table functions, JSON|
|2019||SQL:2019||Adds Part 15, multidimensional arrays (MDarray type and operators)|
The standard is commonly denoted by the pattern: ISO/IEC DIS 9075-n:yyyy Part n: title, or, as a shortcut, ISO/IEC 9075 (The term 'DIS' is not used in older versions). Interested parties may purchase the standards documents from ISO, IEC, or ANSI. Some old drafts are freely available.
ISO/IEC 9075 is complemented by ISO/IEC 13249: SQL Multimedia and Application Packages and some Technical reports.
The SQL standard is divided into 10 parts, but with gaps in the numbering due to the withdrawal of outdated parts.
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 unified access to typical database applications like text, pictures, data mining, or spatial data.
ISO/IEC 9075 is also accompanied by a series of Technical Reports, published as ISO/IEC TR 19075. These Technical Reports explain the justification for and usage of some features of SQL, giving examples where appropriate. The Technical Reports are non-normative; if there is any discrepancy from 9075, the text in 9075 holds. Currently available 19075 Technical Reports are:
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.
Distributed Relational Database Architecture (DRDA) was designed by a workgroup within IBM from 1988 to 1994. DRDA enables network-connected relational databases to cooperate to fulfill SQL requests.
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. Distributed SQL processing ala DRDA is distinctive from contemporary distributed SQL databases.
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 returns strictly to the original foundation: for example, see The Third Manifesto.
Early specifications did not support major features, such as primary keys. Result sets could not be named, and subqueries had not been defined. These were added in 1992.
The lack of sum types has been described as a roadblock to full use of SQL's user-defined types. JSON support, for example, needed to be added by a new standard in 2016.
The concept of Null is the subject of some debates. The Null marker indicates the absence of a value, and is distinct from a value of 0 for an integer column or an empty string for a text column. The concept of Nulls enforces the 3-valued-logic in SQL, which is a concrete implementation of the general 3-valued logic.
Another popular criticism is that it allows duplicate rows, making integration with languages such as Python, whose data types might make accurately representing the data difficult, in terms of parsing and by the absence of modularity.
This is usually avoided by declaring a primary key, or a unique constraint, with one or more columns that uniquely identify a row in the table.
In a similar sense to object–relational impedance mismatch, a mismatch occurs between the declarative SQL language and the procedural languages in which SQL is typically embedded.
The SQL standard defines three kinds of data types:
Constructed types are one of ARRAY, MULTISET, REF(erence), or ROW. User-defined types are comparable to classes in object-oriented language with their own constructors, observers, mutators, methods, inheritance, overloading, overwriting, interfaces, and so on. Predefined data types are intrinsically supported by the implementation.
We changed the original name "SEQUEL" to SQL because we got a letter from somebody’s lawyer that said the name "SEQUEL" belonged to them. We shortened it to SQL, for Structured Query Language, and the product was known as SQL/DS.
PostgreSQL prides itself in standards compliance. Its SQL implementation strongly conforms to the ANSI-SQL:2008 standard
DATEvalue, Oracle stores the following information: century, year, month, date, hour, minute, and second
The datetime data types are
Do not define columns with the following SQL/DS and DB2 data types, because they have no corresponding Oracle data type:...
SQL (correctly pronounced "ess cue ell," instead of the somewhat common "sequel")...