SQL#Queries

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 original name SEQUEL, which is widely regarded as a pun on QUEL, the query language of Ingres,{{Cite web |last=Starkey |first=Jim |title=Dynamic SQL, Plumbing, and the Internal API |url=https://www.ibphoenix.com/resources/documents/design/doc_123 |access-date=19 January 2023 |website=www.ibphoenix.com |archive-date=19 January 2023 |archive-url=https://web.archive.org/web/20230119035452/https://www.ibphoenix.com/resources/documents/design/doc_123 |url-status=live }} 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.{{Cite web |last=Yasar |first=Kinza |last2=Loshin |first2=Peter |last3=Sirkin |first3=Jessica |title=What is Structured Query Language (SQL)? {{!}} Definition from TechTarget |url=https://www.techtarget.com/searchdatamanagement/definition/SQL |url-status=live |archive-url=https://web.archive.org/web/20250310030105/https://www.techtarget.com/searchdatamanagement/definition/SQL |archive-date=10 March 2025 |access-date=25 March 2025 |website=Search Data Management |publisher=Informa TechTarget}}

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,{{cite journal|last1=Chamberlin|first1=Donald|title=Early History of SQL|journal=IEEE Annals of the History of Computing|date=2012|volume=34|issue=4|pages=78–82|doi=10.1109/MAHC.2012.61|s2cid=1322572}} 2016 and most recently, 2023.{{cite web |title=ISO - ISO/IEC JTC 1/SC 32 - Data management and interchange |url=https://www.iso.org/committee/45342/x/catalogue/p/1/u/0/w/0/d/0 |website=www.iso.org |access-date=2 January 2021 |archive-date=16 March 2017 |archive-url=https://web.archive.org/web/20170316024321/https://www.iso.org/committee/45342/x/catalogue/p/1/u/0/w/0/d/0 |url-status=live }}

{{SQL language revisions}}

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. PostgreSQL and Mimer SQL 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,{{cite web|url=https://www.postgresql.org/docs/current/static/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS|title=4.1. Lexical Structure|date=2018|website=PostgreSQL documentation|access-date=11 December 2018|archive-date=5 October 2018|archive-url=https://web.archive.org/web/20181005190818/https://www.postgresql.org/docs/current/static/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS|url-status=live}} which says that unquoted names should be folded to upper case.{{cite web|url=http://www.contrib.andrew.cmu.edu/~shadow/sql/sql1992.txt|title=(Second Informal Review Draft) ISO/IEC 9075:1992, Database Language SQL, Section 5.2, syntax rule 11|date=30 July 1992|access-date=8 October 2009|archive-date=21 June 2006|archive-url=https://web.archive.org/web/20060621035823/http://www.contrib.andrew.cmu.edu/%7Eshadow/sql/sql1992.txt|url-status=live}} Thus, according to the standard, Foo should be equivalent to FOO, not foo.

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, 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 the lack of portability between database systems include:

• The complexity and size of the SQL standard means that most implementers do not support the entire standard.
• The SQL standard does not specify the database behavior in some important areas (e.g., indices, file storage), leaving implementations to decide how to behave.
• The SQL standard defers some decisions to individual implementations, such as how to name a results column that was not named explicitly.{{cite book |last1=Date |first1=Chris J. |title=Relational Theory for Computer Professionals: What Relational Databases are Really All About |date=2013 |publisher=O'Reilly Media |location=Sebastopol, Calif |isbn=978-1-449-36943-9 |edition=1.}}{{rp|207}}
• 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.
• Little commercial incentive exists for vendors to make changing database suppliers easier (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 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: {{IPAc-en|ˌ|ɛ|s|ˌ|k|juː|ˈ|ɛ|l}} ("ess cue el"). Regardless, many English-speaking database professionals (including Donald Chamberlin himself) use the acronym-like pronunciation of {{IPAc-en|ˈ|s|iː|k|w|əl}} ("sequel"), mirroring the language's prerelease development name, "SEQUEL".
The SQL standard has gone through a number of revisions:

The standard is commonly denoted by the pattern: ISO/IEC 9075-n:yyyy Part n: title, or, as a shortcut, ISO/IEC 9075. Interested parties may purchase the standards documents from ISO,{{cite web | url = https://www.iso.org/search.html | title = ISO/IEC 9075 | access-date = 9 August 2022 | archive-date = 12 August 2022 | archive-url = https://web.archive.org/web/20220812025804/https://www.iso.org/search.html | url-status = live }} 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.

{{Main|SQL syntax}}

{{Image frame|content=

\underbrace{\left. \begin{array}{rl} \textstyle\mathtt{UPDATE~clause\mathtt{:}} & \{ \mathtt{UPDATE\ \overbrace{\mathtt{countries}}^\mathtt{table}} \} \\

\textstyle\mathtt{SET~clause:} & \{ {\mathtt{SET\ \overbrace{\mathtt{population}}^\mathtt{column} =~} \overbrace{\mathtt{{population} + \underbrace{\mathtt{1}}_\mathtt{literal}}}^\mathtt{expression}} \} \\

\textstyle\mathtt{WHERE~clause:} & \{ {\mathtt{WHERE\ \underbrace{\overbrace{\mathtt{name}}^\mathtt{column} \mathtt{=} \overbrace{{\overbrace{\mathtt{'USA'}}^\mathtt{literal}}}^\mathtt{expression}}_\mathtt{predicate}}\}{\texttt{;}}}

\end{array}

\right \}{\textstyle\texttt{statement}}}_{\textstyle\mathtt{SQL~query}}

|width=500|caption=A chart showing several of the SQL language elements comprising 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.)
• 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.

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.

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. Microsoft 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, JavaScript (PL/V8) and C.

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.

{{Div col}}

• .QL: object-oriented Datalog
• 4D Query Language (4D QL)
• 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.
• 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
• JavaScript: MongoDB implements its query language in a JavaScript API.
• 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, closer to tuple relational calculus than SQL
• XQuery

{{Div col end}}

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.{{cite journal|last1=Reinsch, R.|title=Distributed database for SAA|journal=IBM Systems Journal|date=1988|volume=27|issue=3|pages=362–389|doi=10.1147/sj.273.0362}}{{cite book|title=Distributed Relational Database Architecture Reference|date=1990|publisher=IBM Corp. SC26-4651-0}}

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 by Hugh Darwen and C.J. Date (2006, {{ISBN|0-321-39942-0}}).

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.{{cite web |last1=Brandon |first1=Jamie |title=Against SQL |url=https://scattered-thoughts.net/writing/against-sql/ |access-date=2 August 2021 |language=en |date=July 2021}}

The concept of Null is the subject of some debate. 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 sense similar to object–relational impedance mismatch, a mismatch occurs between the declarative SQL language and the procedural languages in which SQL is typically embedded.{{Citation needed|date=February 2024}}

The SQL standard defines three kinds of data types (chapter 4.1.1 of SQL/Foundation):

• predefined data types
• constructed types
• user-defined 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.

• Character types
• Character (CHAR)
• Character varying (VARCHAR)
• Character large object (CLOB)
• National character types
• National character (NCHAR)
• National character varying (NCHAR VARYING)
• National character large object (NCLOB)
• Binary types
• Binary (BINARY)
• Binary varying (VARBINARY)
• Binary large object (BLOB)
• Numeric types
• Exact numeric types (NUMERIC, DECIMAL, SMALLINT, INTEGER, BIGINT)
• Approximate numeric types (FLOAT, REAL, DOUBLE PRECISION)
• Decimal floating-point type (DECFLOAT)
• Datetime types (DATE, TIME, TIMESTAMP)
• Interval type (INTERVAL)
• Boolean
• XML (see SQL/XML){{Cite web |last= |date=November 2003 |title=SQL 2003 Standard Support in Oracle Database 10g |url=https://www.oracle.com/technetwork/database/sql-2003-twp-129141.pdf |access-date=27 March 2024 |website=Oracle |publisher=Oracle Corporation |language=en-us |archive-date=27 March 2024 |archive-url=https://web.archive.org/web/20240327155056/https://www.oracle.com/technetwork/database/sql-2003-twp-129141.pdf |url-status=live }} XML supported was added in ANSI SQL 2003, part 14.
• JSON

{{div col|colwidth=20em}}

• Object database
• List of relational database management systems
• Comparison of relational database management systems
• Comparison of object–relational database management systems
• Query by Example
• SQL reserved words
• SQL syntax
• Oracle PL/SQL
• Microsoft Transact-SQL (T-SQL)
• Online transaction processing (OLTP)
• Online analytical processing (OLAP)
• Data warehouse
• Relational data stream management system
• NoSQL
• MUMPS
• Hierarchical database model
• Star schema
• Snowflake schema

{{div col end}}

{{notelist}}

{{Reflist|30em|refs=

{{cite web | last = Paul | first = Ryan | title = A guided tour of the Microsoft Command Shell | url = https://arstechnica.com/business/news/2005/10/msh.ars/4 | website = Ars Technica | date = 24 October 2005 | access-date = 10 April 2011 }}

{{cite web | url = https://www.iana.org/assignments/media-types/application/sql | title = Media Type registration for application/sql | publisher = Internet Assigned Numbers Authority | date = 10 April 2013 | access-date = 10 April 2013 | archive-date = 7 May 2013 | archive-url = https://web.archive.org/web/20130507140101/http://www.iana.org/assignments/media-types/application/sql | url-status = live }}

{{cite web | url = http://tools.ietf.org/html/rfc6922 | title = The application/sql Media Type, RFC 6922 | page = 3 | publisher = Internet Engineering Task Force | date = April 2013 | doi = 10.17487/RFC6922 | access-date = 10 April 2013 | last1 = Shafranovich | first1 = Y. | archive-date = 13 October 2014 | archive-url = https://web.archive.org/web/20141013172428/http://tools.ietf.org/html/rfc6922 | url-status = live }}

{{ cite book | last = Beaulieu | first = Alan | title = Learning SQL | editor = Mary E Treseler | publisher = O'Reilly | location = Sebastopol, CA, USA | date = April 2009 | edition = 2nd | isbn = 978-0-596-52083-0 }}

{{ cite journal | last = Codd | first = Edgar F. | title = A Relational Model of Data for Large Shared Data Banks | journal = Communications of the ACM | volume = 13 | issue = 6 | pages = 377–87 | date = June 1970 | doi = 10.1145/362384.362685 | citeseerx = 10.1.1.88.646 | s2cid = 207549016 }}

{{cite news | last = Chapple | first = Mike | title = SQL Fundamentals | work = Databases | publisher = About.com | url = http://databases.about.com/od/sql/a/sqlfundamentals.htm | access-date = 28 January 2009 | archive-date = 22 February 2009 | archive-url = https://web.archive.org/web/20090222225300/http://databases.about.com/od/sql/a/sqlfundamentals.htm | url-status = dead }}

{{cite web | title = Structured Query Language (SQL) | publisher = International Business Machines | url = http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=com.ibm.db2.udb.admin.doc/doc/c0004100.htm | date = 27 October 2006 | access-date = 10 June 2007 }}

{{cite web | url = https://www.iso.org/standard/16661.html | title = ISO 9075:1987: Information technology – Database languages – SQL – Part 1: Framework (SQL/Framework) | date = 1 June 1987 | access-date = 7 May 2019 | archive-date = 7 May 2019 | archive-url = https://web.archive.org/web/20190507214157/https://www.iso.org/standard/16661.html | url-status = live }}

{{ cite journal | last1 = Chamberlin | first1 = Donald D | last2 = Boyce | first2 = Raymond F | title = SEQUEL: A Structured English Query Language | journal = Proceedings of the 1974 ACM SIGFIDET Workshop on Data Description, Access and Control | pages = 249–64 | publisher = Association for Computing Machinery | year = 1974 | url = http://www.almaden.ibm.com/cs/people/chamberlin/sequel-1974.pdf | access-date = 9 June 2007 | archive-url=https://web.archive.org/web/20070926212100/http://www.almaden.ibm.com/cs/people/chamberlin/sequel-1974.pdf |archive-date=26 September 2007 |url-status=dead }}

{{cite book | last = Oppel | first = Andy | title = Databases Demystified | publisher = McGraw-Hill Osborne Media | date = 27 February 2004 | location = San Francisco, CA | pages = 90–1 | url = http://www.mhprofessional.com/product.php?cat=112&isbn=0071469605 | isbn = 978-0-07-146960-9 | archive-date = 14 January 2012 | access-date = 12 May 2011 | archive-url = https://web.archive.org/web/20120114180544/http://www.mhprofessional.com/product.php?cat=112&isbn=0071469605 | url-status = live }}

{{cite web | title = History of IBM, 1978 | work = IBM Archives | date = 23 January 2003 | publisher = IBM | url = http://www-03.ibm.com/ibm/history/history/year_1978.html | archive-url = https://web.archive.org/web/20050117192541/http://www-03.ibm.com/ibm/history/history/year_1978.html | url-status = dead | archive-date = 17 January 2005 | access-date = 9 June 2007 }}

ANSI/ISO/IEC International Standard (IS). Database Language SQL—Part 2: Foundation (SQL/Foundation). 1999.

{{cite web | title = PostgreSQL server programming | work = PostgreSQL 9.1 official documentation | publisher = postgresql.org | year = 2011 | url = http://www.postgresql.org/docs/9.1/static/server-programming.html | access-date = 9 March 2012 | archive-date = 2 March 2012 | archive-url = https://web.archive.org/web/20120302074948/http://www.postgresql.org/docs/9.1/static/server-programming.html | url-status = live }}

{{cite web |url=http://lbd.udc.es/jornadas2011/actas/PROLE/PROLE/S5/13_article.pdf |title=Outer Joins in a Deductive Database System |author=Fernando Saenz-Perez |website=Lbd.udc.es |access-date=16 January 2017 |archive-date=9 August 2016 |archive-url=https://web.archive.org/web/20160809225439/http://lbd.udc.es/jornadas2011/actas/PROLE/PROLE/S5/13_article.pdf |url-status=live }}

{{cite web | title = About PostgreSQL | work = PostgreSQL 9.1 official website | publisher = PostgreSQL Global Development Group | year = 2012 | url = http://www.postgresql.org/about/ | quote = PostgreSQL prides itself in standards compliance. Its SQL implementation strongly conforms to the ANSI-SQL:2008 standard | access-date = 9 March 2012 | archive-date = 9 March 2012 | archive-url = https://web.archive.org/web/20120309174528/http://www.postgresql.org/about/ | url-status = live }}

{{cite web | title = Mimer SQL, Built on Standards | work = Mimer SQL official website | publisher = Mimer Information Technology | year = 2009 | url = http://developer.mimer.com/features/feature_6.htm | access-date = 11 December 2018 | archive-date = 3 May 2016 | archive-url = https://web.archive.org/web/20160503020216/http://developer.mimer.com/features/feature_6.htm | url-status = live }}

{{cite book | first1 = Diana | last1 = Lorentz | first2 = Mary Beth | last2 = Roeser | first3 = Sundeep | last3 = Abraham | first4 = Angela | last4 = Amor | first5 = Geeta | last5 = Arora | first6 = Vikas | last6 = Arora | first7 = Lance | last7 = Ashdown | first8 = Hermann | last8 = Baer | first9 = Shrikanth | last9 = Bellamkonda | series = Oracle Database Documentation Library | publisher = Oracle USA, Inc | place = Redwood City, CA | title = Oracle Database SQL Language Reference 11g Release 2 (11.2) | chapter = Basic Elements of Oracle SQL: Data Types | orig-year = 1996 | date = October 2010 | access-date = 29 December 2010 | chapter-url = http://download.oracle.com/docs/cd/E11882_01/server.112/e17118/sql_elements001.htm#sthref154 | quote = For each DATE value, Oracle stores the following information: century, year, month, date, hour, minute, and second | archive-date = 20 November 2010 | archive-url = https://web.archive.org/web/20101120055711/http://download.oracle.com/docs/cd/E11882_01/server.112/e17118/sql_elements001.htm#sthref154 | url-status = live }}

{{cite book | first1 = Diana | last1 = Lorentz | first2 = Mary Beth | last2 = Roeser | first3 = Sundeep | last3 = Abraham | first4 = Angela | last4 = Amor | first5 = Geeta | last5 = Arora | first6 = Vikas | last6 = Arora | first7 = Lance | last7 = Ashdown | first8 = Hermann | last8 = Baer | first9 = Shrikanth | last9 = Bellamkonda | series = Oracle Database Documentation Library | publisher = Oracle USA, Inc | place = Redwood City, CA | title = Oracle Database SQL Language Reference 11g Release 2 (11.2) | chapter = Basic Elements of Oracle SQL: Data Types | orig-year = 1996 | date = October 2010 | access-date = 29 December 2010 | chapter-url = http://download.oracle.com/docs/cd/E11882_01/server.112/e17118/sql_elements001.htm#sthref154 | quote = The datetime data types are DATE... | archive-date = 20 November 2010 | archive-url = https://web.archive.org/web/20101120055711/http://download.oracle.com/docs/cd/E11882_01/server.112/e17118/sql_elements001.htm#sthref154 | url-status = live }}

{{cite book | first1 = Diana | last1 = Lorentz | first2 = Mary Beth | last2 = Roeser | first3 = Sundeep | last3 = Abraham | first4 = Angela | last4 = Amor | first5 = Geeta | last5 = Arora | first6 = Vikas | last6 = Arora | first7 = Lance | last7 = Ashdown | first8 = Hermann | last8 = Baer | first9 = Shrikanth | last9 = Bellamkonda | series = Oracle Database Documentation Library | publisher = Oracle USA, Inc | place = Redwood City, CA | title = Oracle Database SQL Language Reference 11g Release 2 (11.2) | chapter = Basic Elements of Oracle SQL: Data Types | orig-year = 1996 | date = October 2010 | access-date = 29 December 2010 | chapter-url = http://download.oracle.com/docs/cd/E11882_01/server.112/e17118/sql_elements001.htm#i54335 | quote = Do not define columns with the following SQL/DS and DB2 data types, because they have no corresponding Oracle data type:... TIME | archive-date = 20 November 2010 | archive-url = https://web.archive.org/web/20101120055711/http://download.oracle.com/docs/cd/E11882_01/server.112/e17118/sql_elements001.htm#i54335 | url-status = live }}

{{cite book | chapter-url = http://special.lib.umn.edu/findaid/xml/cbi00168.xml | publisher = American National Standards Institute | title = X3H2 Records, 1978–95 | chapter = Finding Aid | archive-date = 19 June 2010 | access-date = 26 April 2008 | archive-url = https://web.archive.org/web/20100619143221/http://special.lib.umn.edu/findaid/xml/cbi00168.xml | url-status = live }}

{{cite web | last = Doll | first = Shelley | title = Is SQL a Standard Anymore? | work = TechRepublic's Builder.com | publisher = TechRepublic | date = 19 June 2002 | url = http://articles.techrepublic.com.com/5100-10878_11-1046268.html | access-date = 12 April 2016 | archive-url = https://web.archive.org/web/20120705163024/http://www.techrepublic.com/article/is-sql-a-standard-anymore/1046268 | archive-date = 5 July 2012 }}

{{cite web | last = Gillespie | first = Patrick | url = http://patorjk.com/blog/2012/01/26/pronouncing-sql-s-q-l-or-sequel/ | title = Pronouncing SQL: S-Q-L or Sequel? | access-date = 12 February 2012 | archive-date = 27 May 2012 | archive-url = https://web.archive.org/web/20120527131959/http://patorjk.com/blog/2012/01/26/pronouncing-sql-s-q-l-or-sequel/ | url-status = live }}

{{cite book | title = Understanding the New SQL: A Complete Guide | last = Melton | first = Jim | author2 = Alan R Simon | year = 1993 | publisher = Morgan Kaufmann | isbn = 978-1-55860-245-8 | page = [https://archive.org/details/understandingnew00melt/page/536 536] | chapter = 1.2. What is SQL? | quote = SQL (correctly pronounced "ess cue ell," instead of the somewhat common "sequel")... | chapter-url-access = registration | chapter-url = https://archive.org/details/understandingnew00melt | url = https://archive.org/details/understandingnew00melt/page/536 }}

{{ cite book | title = SQL/XML:2006 - Evaluierung der Standardkonformität ausgewählter Datenbanksysteme | last = Wagner | first = Michael | year = 2010 | publisher = Diplomica Verlag | isbn = 978-3-8366-9609-8 | page = 100 }}

{{ cite web |date=July 2008 |title=SQL:2008 now an approved ISO international standard |publisher=Sybase |url=http://iablog.sybase.com/paulley/2008/07/sql2008-now-an-approved-iso-international-standard/ |url-status=dead |archive-url=https://web.archive.org/web/20110628130925/http://iablog.sybase.com/paulley/2008/07/sql2008-now-an-approved-iso-international-standard/ |archive-date=28 June 2011 }}

{{citation | url = http://www.contrib.andrew.cmu.edu/~shadow/sql/sql1992.txt | format = text | title = SQL:1992 draft | access-date = 8 October 2009 | archive-date = 21 June 2006 | archive-url = https://web.archive.org/web/20060621035823/http://www.contrib.andrew.cmu.edu/%7Eshadow/sql/sql1992.txt | url-status = live }}

{{ citation | url = https://www.wiscorp.com/sql20nn.zip | format = Zip | title = SQL:2011 draft | publisher = Whitemarsh Information Systems Corporation | archive-url = https://web.archive.org/web/20230525220603/https://www.wiscorp.com/sql20nn.zip | archive-date = 25 May 2023 }}

{{ cite web | title = What's new in SQL:2011 | url = https://sigmodrecord.org/publications/sigmodRecord/1203/pdfs/10.industry.zemke.pdf | author = Fred Zemke |publisher=Oracle Corporation | year = 2012 }}

{{ cite journal | title = Temporal features in SQL:2011 | url = http://cs.ulb.ac.be/public/_media/teaching/infoh415/tempfeaturessql2011.pdf | author = Krishna Kulkarni, Jan-Eike Michels |journal=SIGMOD Record | date = September 2012 |volume=41 |number=3 }}

}}

{{Refbegin}}

• {{cite journal|last = Codd|first = Edgar F|date = June 1970|title = A Relational Model of Data for Large Shared Data Banks|journal = Communications of the ACM|volume = 13|issue = 6|pages = 377–87|doi = 10.1145/362384.362685|s2cid = 207549016|doi-access = free}}
• 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}}

{{Refend}}

• [http://www.mcjones.org/System_R/SQL_Reunion_95/sqlr95.html 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.
• [http://special.lib.umn.edu/findaid/xml/cbi00168.xml American National Standards Institute. X3H2 Records, 1978–1995] Charles Babbage Institute Collection documents the H2 committee's development of the NDL and SQL standards.
• [http://purl.umn.edu/107215 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.

{{SQL}}

{{Navboxes|list=

{{Databases}}

{{Programming languages}}

{{Query languages}}

{{IBM}}

{{ISO standards}}

}}

{{Subject bar|portal1=Computer programming|commons=Category:Structured Query Language|v=SQL|b=Structured Query Language|d=y}}

{{Authority control}}

Category:Articles with example SQL code

Category:Data modeling languages

Category:Declarative programming languages

Category:Programming languages with an ISO standard

Category:Query languages

Category:Relational database management systems

Category:Data-centric programming languages

Category:Programming languages created in 1974

Category:Table-oriented programming

Category:Database management systems