CACrown ArchivesThe cinema collection
Menu
Research dossier · General Reference

SQL

relational database language that allows to extract from data tables a series of records with selection, sorting and computation criteria, or to update, delete or add records

Cross-disciplinary reference desk with index cards, atlas, dictionary and catalogue
General referenceInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionSep 13, 2026
Entity authorityQ47607
Source-derived summary

Structured Query Language (SQL) (pronounced S-Q-L; or alternatively as "sequel") is a domain-specific language used to manage data, especially in a relational database management system (RDBMS). It is particularly useful in handling structured data, i.e., data incorporating relations among entities and variables.

Introduced in the 1970s, SQL offered 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, i.e., 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: data query language (DQL), data definition language (DDL), data control language (DCL), and data manipulation language (DML).

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, SQL became the most widely used database language.

Editorial summary

“SQL” enters the record as relational database language that allows to extract from data tables a series of records with selection, sorting and computation criteria, or to update, delete or add records. Crown Archives preserves that source wording while asking what relational, database and language can confirm, complicate or overturn.

Editorial reviewA dependable orientation record for establishing vocabulary, names and a first evidence trail. The current lead gives the account dated anchors—1970—that can be checked directly. The authority record carries competing date values—1974, 1986—which should remain separate until their references and qualifiers are resolved. Its strongest next move is a source search built around relational, database and language.
Editorial analysis

Why this record matters

“SQL” is worth following because a concise public description often conceals a longer documentary argument. Here, relational, database and language provides the most credible route into that argument.

Evidence profile

Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Sep 13, 2026. The linked authority identifier is Q47607. The Library of Congress control number is sh86006628. 1 of 4 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1970.

Critical limits

The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.

Best used for
  • Subject orientation
  • Search vocabulary
  • Locating named sources
Verify next

The closest primary source, responsible institution and strongest cited specialist reference.

Three-step research path

  1. Establish the record: confirm the title “SQL”, its source revision and the description used here.
  2. Expand the search: follow SQL primary sources, SQL archive and relational research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “SQL”?
  2. What terminology or title could unlock a more precise catalogue search?
  3. Which institution is responsible for the underlying evidence?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from SQL” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.