banner



Home  ›  What Is Sql Database Used For

What Is Sql Database Used For

Written By Tuesday, May 17, 2022 Add Comment Edit

Language for direction and utilize of relational databases

SQL (Structured Query Language)
Paradigm Declarative
Family Query language
Designed by Donald D. Chamberlin
Raymond F. Boyce
Developer ISO/IEC
First appeared 1974; 48 years agone  (1974)
Stable release

SQL:2016 / December 2016; v years agone  (2016-12)

Typing subject area Static, strong
OS Cross-platform
Website www.iso.org/standard/63555.html
Major implementations
Many
Dialects
  • SQL-86
  • SQL-89
  • SQL-92
  • SQL:1999
  • SQL:2003
  • SQL:2006
  • SQL:2008
  • SQL:2011
  • SQL:2016
Influenced by
Datalog
Influenced
CQL, LINQ, SPARQL, SOQL, PowerShell,[1] JPQL, jOOQ, N1QL
  • Structured Query Language at Wikibooks
SQL (file format)
Filename extension

.sql
Internet media blazon

application/sql[2] [iii]

Developed by ISO/IEC
Initial release 1986 (1986)
Type of format Database
Standard ISO/IEC 9075
Open up format? Yeah
Website www.iso.org/standard/63555.html

SQL ( S-Q-L,[4] "sequel"; Structured Query Linguistic communication)[5] is a domain-specific linguistic communication 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). Information technology is peculiarly useful in handling structured data, i.east. 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, information technology eliminates the need to specify how to achieve 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,[6] which may be informally classed equally sublanguages, unremarkably: a data query language (DQL),[a] a data definition language (DDL),[b] a data control language (DCL), and a information manipulation language (DML).[c] [7] The telescopic of SQL includes data query, data manipulation (insert, update and delete), data definition (schema cosmos and modification), and data access command. Although SQL is substantially a declarative linguistic communication (4GL), it also includes procedural elements.

SQL was ane of the first commercial languages to employ Edgar F. Codd'southward relational model. The model was described in his influential 1970 paper, "A Relational Model of Data for Large Shared Data Banks".[8] Despite not entirely adhering to the relational model as described by Codd, it became the most widely used database linguistic communication.[ix] [10]

SQL became a standard of the American National Standards Institute (ANSI) in 1986 and of the International Organization for Standardization (ISO) in 1987.[xi] Since and then, the standard has been revised to include a larger set of features. Despite the existence of standards, most SQL lawmaking requires at least some changes before being ported to different database systems.

History [edit]

SQL was initially developed at IBM by Donald D. Chamberlin and Raymond F. Boyce after learning about the relational model from Edgar F. Codd[12] in the early 1970s.[13] This version, initially called SEQUEL (Structured English language Query Language), was designed to manipulate and retrieve information stored in IBM'due south original quasirelational database management organisation, System R, which a grouping at IBM San Jose Inquiry Laboratory had adult during the 1970s.[13]

Chamberlin and Boyce'southward get-go attempt at a relational database linguistic communication was SQUARE (Specifying Queries in A Relational Surround), just information technology was difficult to use due to subscript/superscript note. Afterwards moving to the San Jose Research Laboratory in 1973, they began work on a sequel to Foursquare.[12] The proper noun SEQUEL was afterwards changed to SQL (dropping the vowels) considering "SEQUEL" was a trademark of the UK-based Hawker Siddeley Dynamics Engineering Limited company.[14] The label SQL afterward became the acronym for Structured Query Language.

Afterward testing SQL at customer test sites to determine the usefulness and practicality of the organization, IBM began developing commercial products based on their System R epitome, including Arrangement/38, SQL/DS, and IBM Db2, which were commercially bachelor in 1979, 1981, and 1983, respectively.[xv]

In the late 1970s, Relational Software, Inc. (now Oracle Corporation) saw the potential of the concepts described by Codd, Chamberlin, and Boyce, and adult their own SQL-based RDBMS with aspirations of selling it to the U.S. Navy, Cardinal 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 Linguistic communication SQL" language definition. New versions of the standard were published in 1989, 1992, 1996, 1999, 2003, 2006, 2008, 2011,[12] and most recently, 2016.[16]

Syntax [edit]

U P D A T E c l a u s e { U P D A T E c o u n t r y S E T c 50 a u s e { Southward Eastward T p o p u l a t i o northward = p o p u l a t i o n + 1 ⏞ due east ten p r e s s i o n West H E R E c l a u s due east { W H E R E n a m due east = ′ U South A ′ ⏞ east x p r e s s i o n ⏟ p r e d i c a t e ; } argument {\displaystyle \left.{\brainstorm{array}{rl}\textstyle {\mathtt {UPDATE~clause}}&\{{\mathtt {UPDATE\ country}}\\\textstyle {\mathtt {Fix~clause}}&\{{\mathtt {Gear up\ population=~}}\overbrace {\mathtt {population+one}} ^{\mathtt {expression}}\\\textstyle {\mathtt {WHERE~clause}}&\{{\mathtt {WHERE\ \underbrace {{name=}\overbrace {'United states of america'} ^{expression}} _{predicate};}}\end{array}}\right\}{\textstyle {\texttt {statement}}}}

A nautical chart showing several of the SQL language elements comprising a unmarried argument

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

  • Clauses, which are constituent components of statements and queries. (In some cases, these are optional.)[17]
  • Expressions, which can produce either scalar values, or tables consisting of columns and rows of data
  • Predicates, which specify weather condition that can be evaluated to SQL three-valued logic (3VL) (truthful/false/unknown) or Boolean truth values and are used to limit the furnishings of statements and queries, or to alter program flow.
  • Queries, which call up the data based on specific criteria. This is an important element of SQL.
  • Statements, which may have a persistent issue on schemata and data, or may control transactions, plan menses, connections, sessions, or diagnostics.
    • SQL statements also include the semicolon (";") argument terminator. Though not required on every platform, it is defined as a standard function of the SQL grammar.
  • Insignificant whitespace is generally ignored in SQL statements and queries, making it easier to format SQL code for readability.

Procedural extensions [edit]

SQL is designed for a specific purpose: to query data contained in a relational database. SQL is a ready-based, declarative programming linguistic communication, not an imperative programming language like C or Basic. Nonetheless, extensions to Standard SQL add procedural programming language functionality, such equally control-of-menses constructs. These include:

Source Abridgement Total proper noun
ANSI/ISO Standard SQL/PSM SQL/Persistent Stored Modules
Interbase / Firebird PSQL Procedural SQL
IBM Db2 SQL PL SQL Procedural Linguistic communication (implements SQL/PSM)
IBM Informix SPL Stored Procedural Language
IBM Netezza NZPLSQL[18] (based on Postgres PL/pgSQL)
Invantive PSQL[19] 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)[xx]
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
SAP HANA SQLScript SQLScript
Sybase Watcom-SQL SQL Anywhere Watcom-SQL Dialect
Teradata SPL Stored Procedural Language

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 Coffee 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 diverseness of languages—including Perl, Python, Tcl, JavaScript (PL/V8) and C.[21]

Interoperability and standardization [edit]

Overview [edit]

SQL implementations are incompatible between vendors and do not necessarily completely follow standards. In item, date and fourth dimension syntax, string concatenation, NULLs, and comparison case sensitivity vary from vendor to vendor. Particular exceptions are PostgreSQL[22] and Mimer SQL[23] 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 example in PostgreSQL is incompatible with the SQL standard,[24] which says that unquoted names should exist folded to upper case.[25] Thus, Foo should be equivalent to FOO not foo co-ordinate to the standard.

Popular implementations of SQL commonly omit support for bones features of Standard SQL, such as the Appointment or TIME data types. The nigh obvious such examples, and incidentally the about pop commercial and proprietary SQL DBMSs, are Oracle (whose DATE behaves as DATETIME,[26] [27] and lacks a TIME type)[28] and MS SQL Server (before the 2008 version). As a consequence, SQL lawmaking tin rarely be ported between database systems without modifications.

Reasons for incompatibility [edit]

Several reasons for this lack of portability between database systems include:

  • The complexity and size of the SQL standard means that nearly implementers practice not back up the entire standard.
  • The standard does not specify database behavior in several of import areas (east.thousand. indices, file storage...), leaving implementations to decide how to behave.
  • The SQL standard precisely specifies the syntax that a conforming database arrangement must implement. However, the standard'southward specification of the semantics of linguistic communication constructs is less well-defined, leading to ambivalence.
  • Many database vendors take big 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 interruption astern compatibility.
  • Fiddling commercial incentive exists for vendors to make changing database suppliers easier (encounter vendor lock-in).
  • Users evaluating database software tend to place other factors such equally functioning higher in their priorities than standards conformance.

Standardization history [edit]

SQL was adopted as a standard by the ANSI in 1986 as SQL-86[29] and the ISO in 1987.[11] It is maintained by ISO/IEC JTC one, Information engineering science, Subcommittee SC 32, Information direction and interchange.

Until 1996, the National Found of Standards and Engineering science (NIST) data-management standards programme certified SQL DBMS compliance with the SQL standard. Vendors at present self-certify the compliance of their products.[30]

The original standard declared that the official pronunciation for "SQL" was an initialism: ("ess cue el").[nine] Regardless, many English-speaking database professionals (including Donald Chamberlin himself[31]) utilize the acronym-similar pronunciation of ("sequel"),[32] mirroring the language's prerelease evolution name, "SEQUEL".[xiii] [14] [31]
The SQL standard has gone through a number of revisions:

Year Name Alias Comments
1986 SQL-86 SQL-87 Get-go formalized by ANSI
1989 SQL-89 FIPS 127-1 Modest revision that added integrity constraints adopted every bit 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.k. transitive closure), triggers, support for procedural and control-of-period 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 exist used with XML. It defines ways of importing and storing XML data in an SQL database, manipulating information technology within the database, and publishing both XML and conventional SQL data in XML form. In addition, information technology lets applications integrate queries into their SQL code with XQuery, the XML Query Language published by the World Broad Spider web Consortium (W3C), to concurrently access ordinary SQL-data and XML documents.[33]
2008 SQL:2008 Legalizes ORDER BY outside cursor definitions. Adds INSTEAD OF triggers, TRUNCATE statement,[34] FETCH clause
2011 SQL:2011 Adds temporal information (PERIOD FOR)[35] (more information at Temporal database#History). Enhancements for window functions and FETCH clause.[36]
2016 SQL:2016 Adds row pattern matching, polymorphic table functions, JSON
2019 SQL:2019 Adds Part 15, multidimensional arrays (MDarray blazon and operators)

Current standard [edit]

The standard is commonly denoted by the blueprint: ISO/IEC 9075-n:yyyy Function 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 such every bit video, audio, and spatial data. Interested parties may purchase SQL standards documents from ISO,[37] IEC, or ANSI. A draft of SQL:2008 is freely available as a zip archive.[38]

Anatomy of SQL Standard [edit]

The SQL standard is divided into x parts, but with gaps in the numbering due to the withdrawal of outdated parts.

  • ISO/IEC 9075-1:2016 Part 1: Framework (SQL/Framework). Information technology provides logical concepts.[39]
  • ISO/IEC 9075-2:2016 Function 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:2016 Part iii: Phone 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 Coffee come across role x.) SQL/CLI is defined in such a manner that SQL statements and SQL/CLI procedure calls are treated as separate from the calling application's source lawmaking. 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:2016 Role 4: Persistent stored modules (SQL/PSM). It standardizes procedural extensions for SQL, including flow of command, condition treatment, statement status signals and resignals, cursors and local variables, and assignment of expressions to variables and parameters. In addition, SQL/PSM formalizes the annunciation and maintenance of persistent database language routines (east.chiliad., "stored procedures"). This part of the standard consists solely of optional features.
  • ISO/IEC 9075-9:2016 Part 9: Management of External Data (SQL/MED). Information technology provides extensions to SQL that define strange-information wrappers and datalink types to allow SQL to manage external data. External information is data that is attainable to, but not managed by, an SQL-based DBMS. This function of the standard consists solely of optional features.
  • ISO/IEC 9075-10:2016 Part 10: Object language bindings (SQL/OLB). It defines the syntax and semantics of SQLJ, which is SQL embedded in Coffee (run across too part 3). The standard too describes mechanisms to ensure binary portability of SQLJ applications and specifies various Coffee packages and their contained classes. This function of the standard consists solely of optional features. Dissimilar SQL/OLB JDBC defines an API and is non part of the SQL standard.[ commendation needed ]
  • ISO/IEC 9075-eleven:2016 Part 11: Information and definition schemas (SQL/Schemata). It defines the Information Schema and Definition Schema, providing a common ready 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 past SQL-based DBMS implementations, SQL-based DBMS implementation information and sizing items, and the values supported past the DBMS implementations.[40] This part of the standard contains both mandatory and optional features.
  • ISO/IEC 9075-xiii:2016 Role thirteen: SQL Routines and types using the Java TM 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 power to use Java classes as SQL structured user-defined types. This office of the standard consists solely of optional features.
  • ISO/IEC 9075-14:2016 Role 14: XML-Related Specifications (SQL/XML). It specifies SQL-based extensions for using XML in conjunction with SQL. The XML data blazon is introduced, as well as several routines, functions, and XML-to-SQL data blazon mappings to back up manipulation and storage of XML in an SQL database.[33] This office of the standard consists solely of optional features.[ citation needed ]
  • ISO/IEC 9075-15:2019 Part fifteen: Multi-dimensional arrays (SQL/MDA). It specifies a multidimensional array type (MDarray) for SQL, along with operations on MDarrays, MDarray slices, MDarray cells, and related features. This part of the standard consists solely of optional features.

Extensions to the ISO/IEC Standard [edit]

ISO/IEC 9075 is complemented past ISO/IEC 13249 SQL Multimedia and Awarding Packages. This closely related but carve up standard is developed past the same committee. Information technology 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 13249-1:2016 Function ane: Framework
  • ISO/IEC 13249-2:2003 Part two: Full-Text
  • ISO/IEC 13249-3:2016 Part iii: Spatial
  • ISO/IEC 13249-5:2003 Part 5: Yet epitome
  • ISO/IEC 13249-vi:2006 Part 6: Data mining
  • ISO/IEC 13249-7:2013 Part seven: History
  • ISO/IEC 13249-eight:xxxx Role 8: Metadata Registry Access MRA (piece of work in progress)

Technical reports [edit]

ISO/IEC 9075 is also accompanied past 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 whatsoever discrepancy from 9075, the text in 9075 holds. Currently available 19075 Technical Reports are:

  • ISO/IEC TR 19075-1:2011 Part ane: XQuery Regular Expression Support in SQL
  • ISO/IEC TR 19075-2:2015 Part ii: SQL Support for Time-Related Information
  • ISO/IEC TR 19075-3:2015 Office 3: SQL Embedded in Programs using the Java programming language
  • ISO/IEC TR 19075-4:2015 Part 4: SQL with Routines and types using the Java programming language
  • ISO/IEC TR 19075-5:2016 Office 5: Row Design Recognition in SQL
  • ISO/IEC TR 19075-half dozen:2017 Office 6: SQL support for JavaScript Object Notation (JSON)
  • ISO/IEC TR 19075-7:2017 Part 7: Polymorphic table functions in SQL
  • ISO/IEC TR 19075-eight:2019 Function 8: Multi-Dimensional Arrays (SQL/MDA)
  • ISO/IEC TR 19075-9:2020 Function 9: Online analytic processing (OLAP) capabilities

Alternatives [edit]

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)
  • 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 detail for recursive queries.[41]
  • HTSQL: URL based query method
  • IBM Concern System 12 (IBM BS12): 1 of the first fully relational database management systems, introduced in 1982
  • ISBL
  • jOOQ: SQL implemented in Coffee as an internal domain-specific linguistic communication
  • 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 linguistic communication constructs to query collections directly from inside .Internet code
  • Object Query Language
  • QBE (Query By Instance) created by Moshè Zloof, IBM 1977
  • QUEL introduced in 1974 by the U.C. Berkeley Ingres projection, closer to tuple relational calculus than SQL
  • Tutorial D
  • XQuery

Distributed SQL processing [edit]

Distributed Relational Database Architecture (DRDA) was designed past a workgroup within IBM from 1988 to 1994. DRDA enables network-continued relational databases to cooperate to fulfill SQL requests.[42] [43]

An interactive user or program can upshot SQL statements to a local RDB and receive tables of data and status indicators in reply from remote RDBs. SQL statements can also exist compiled and stored in remote RDBs as packages and so invoked by packet name. This is important for the efficient operation of application programs that event complex, high-frequency queries. Information technology 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.

Criticisms [edit]

Design [edit]

SQL deviates in several ways from its theoretical foundation, the relational model and its tuple calculus. In that model, a table is a ready 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 exist replaced with a linguistic communication that returns strictly to the original foundation: for example, encounter The Third Manifesto.

Orthogonality and completeness [edit]

Early specifications did not support major features, such as principal keys. Result sets could not exist named, and subqueries had not been defined. These were added in 1992.[12]

The lack of sum types has been described as a roadblock to total use of SQL's user-defined types. JSON back up, for example, needs to be added past a new standard in 2016.[44]

Null [edit]

The concept of Zero is the subject field of some debates. The Cypher marker indicates the absenteeism of a value, and is singled-out 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 full general three-valued logic.[12]

Duplicates [edit]

Another popular criticism is that it allows indistinguishable rows, making integration with languages such as Python, whose data types might make accurately representing the data difficult,[12] in terms of parsing and by the absence of modularity.[45]

This is commonly avoided by declaring a primary key, or a unique constraint, with one or more columns that uniquely identify a row in the tabular array.

Impedance mismatch [edit]

In a like sense to object–relational impedance mismatch, a mismatch occurs betwixt the declarative SQL linguistic communication and the procedural languages in which SQL is typically embedded.

SQL data types [edit]

The SQL standard defines 3 kinds of data types:[ commendation needed ]

  • predefined data types
  • constructed types
  • user-defined types.

Synthetic types are one of ARRAY, MULTISET, REF(erence), or ROW. User-divers types are comparable to classes in object-oriented linguistic communication with their own constructors, observers, mutators, methods, inheritance, overloading, overwriting, interfaces, and so on. Predefined data types are intrinsically supported by the implementation.

Predefined data types [edit]

  • Character types
  • Character (CHAR)
  • Character varying (VARCHAR)
  • Grapheme large object (CLOB)
  • National graphic symbol types
  • National graphic symbol (NCHAR)
  • National character varying (NCHAR VARYING)
  • National character big object (NCLOB)
  • Binary types
  • Binary (BINARY)
  • Binary varying (VARBINARY)
  • Binary large object (Hulk)
  • Numeric types
  • Exact numeric types (NUMERIC, DECIMAL, SMALLINT, INTEGER, BIGINT)
  • Approximate numeric types (Bladder, REAL, DOUBLE PRECISION)
  • Decimal floating-signal type (DECFLOAT)
  • Datetime types (DATE, TIME, TIMESTAMP)
  • Interval type (INTERVAL)
  • Boolean
  • XML
  • JSON

See also [edit]

  • Wikibook SQL
  • Object database
  • List of relational database direction systems
  • Comparison of relational database management systems
  • Comparing of object–relational database direction systems
  • D (data language specification)
  • Query past Case
  • SQL syntax
  • Oracle PL/SQL
  • Microsoft Transact-SQL (T-SQL)
  • Online transaction processing (OLTP)
  • Online analytical processing (OLAP)
  • Information warehouse
  • Relational information stream management system
  • NoSQL
  • MUMPS
  • Hierarchical database model
  • Star schema
  • Snowflake schema
  • SQL compliance

Notes [edit]

  1. ^ Formally, "SQL-data" statements excluding "SQL-information modify" statements; this is primarily the Select statement.
  2. ^ Formally, "SQL-schema" statements.
  3. ^ Formally, "SQL-data change" statements

References [edit]

  1. ^ Paul, Ryan (24 October 2005). "A guided tour of the Microsoft Command Trounce". Ars Technica . Retrieved 10 April 2011.
  2. ^ "Media Type registration for application/sql". Internet Assigned Numbers Authority. 10 April 2013. Retrieved 10 Apr 2013.
  3. ^ "The application/sql Media Type, RFC 6922". Net Engineering Job Force. Apr 2013. p. three. Retrieved 10 Apr 2013.
  4. ^ Beaulieu, Alan (April 2009). Mary East Treseler (ed.). Learning SQL (2nd ed.). Sebastopol, CA, USA: O'Reilly. ISBN978-0-596-52083-0.
  5. ^ Chamberlin, Donald D. (2001-10-03). "Oral history interview with Donald D. Chamberlin". Retrieved 2020-01-fourteen . We changed the original name "SEQUEL" to SQL because we got a letter of the alphabet from somebody'south lawyer that said the name "SEQUEL" belonged to them. Nosotros shortened information technology to SQL, for Structured Query Language, and the production was known as SQL/DS.
  6. ^ SQL-92, 4.22 SQL-statements, 4.22.1 Classes of SQL-statements "There are at least 5 means of classifying SQL-statements:", 4.22.2, SQL statements classified by function "The following are the principal classes of SQL-statements:"; SQL:2003 4.11 SQL-statements, and later revisions.
  7. ^ Chatham, Mark (2012). Structured Query Language By Example - Volume I: Data Query Linguistic communication. p. viii. ISBN978-ane-29119951-ii.
  8. ^ Codd, Edgar F. (June 1970). "A Relational Model of Data for Large Shared Data Banks". Communications of the ACM. thirteen (half dozen): 377–87. CiteSeerX10.one.1.88.646. doi:ten.1145/362384.362685. S2CID 207549016.
  9. ^ a b Chapple, Mike. "SQL Fundamentals". Databases. Well-nigh.com. Retrieved 2009-01-28 .
  10. ^ "Structured Query Language (SQL)". International Business Machines. October 27, 2006. Retrieved 2007-06-10 .
  11. ^ a b "ISO 9075:1987: Information technology – Database languages – SQL – Role 1: Framework (SQL/Framework)". 1987-06-01.
  12. ^ a b c d e f Chamberlin, Donald (2012). "Early History of SQL". IEEE Annals of the History of Computing. 34 (4): 78–82. doi:10.1109/MAHC.2012.61. S2CID 1322572.
  13. ^ a b c Chamberlin, Donald D; Boyce, Raymond F (1974). "SEQUEL: A Structured English Query Language" (PDF). Proceedings of the 1974 ACM SIGFIDET Workshop on Data Clarification, Admission and Control. Association for Computing Machinery: 249–64. Archived from the original (PDF) on 2007-09-26. Retrieved 2007-06-09 .
  14. ^ a b Oppel, Andy (February 27, 2004). Databases Demystified. San Francisco, CA: McGraw-Hill Osborne Media. pp. ninety–1. ISBN978-0-07-146960-9.
  15. ^ "History of IBM, 1978". IBM Athenaeum. IBM. 23 January 2003. Retrieved 2007-06-09 .
  16. ^ "ISO - ISO/IEC JTC ane/SC 32 - Information management and interchange". www.iso.org . Retrieved 2 January 2021.
  17. ^ ANSI/ISO/IEC International Standard (IS). Database Language SQL—Part 2: Foundation (SQL/Foundation). 1999.
  18. ^ "IBM PureData Arrangement for Analytics, Version 7.0.3".
  19. ^ "Invantive Procedural SQL".
  20. ^ "CREATE PROCEDURE". MariaDB KnowledgeBase . Retrieved 2019-04-23 .
  21. ^ PostgreSQL contributors (2011). "PostgreSQL server programming". PostgreSQL nine.1 official documentation. postgresql.org. Retrieved 2012-03-09 .
  22. ^ PostgreSQL contributors (2012). "About PostgreSQL". PostgreSQL 9.i official website. PostgreSQL Global Development Group. Retrieved March 9, 2012. PostgreSQL prides itself in standards compliance. Its SQL implementation strongly conforms to the ANSI-SQL:2008 standard
  23. ^ "Mimer SQL, Built on Standards". Mimer SQL official website. Mimer Information Engineering. 2009.
  24. ^ "4.i. Lexical Structure". PostgreSQL documentation. 2018.
  25. ^ "(Second Informal Review Draft) ISO/IEC 9075:1992, Database Language SQL, Section 5.2, syntax rule 11". thirty July 1992.
  26. ^ Lorentz, Diana; Roeser, Mary Beth; Abraham, Sundeep; Amor, Angela; Arora, Geeta; Arora, Vikas; Ashdown, Lance; Baer, Hermann; Bellamkonda, Shrikanth (October 2010) [1996]. "Bones Elements of Oracle SQL: Information Types". Oracle Database SQL Language Reference 11g Release 2 (11.2). Oracle Database Documentation Library. Redwood City, CA: Oracle U.s., Inc. Retrieved Dec 29, 2010. For each Engagement value, Oracle stores the following data: century, year, month, appointment, hour, minute, and second
  27. ^ Lorentz, Diana; Roeser, Mary Beth; Abraham, Sundeep; Amor, Angela; Arora, Geeta; Arora, Vikas; Ashdown, Lance; Baer, Hermann; Bellamkonda, Shrikanth (Oct 2010) [1996]. "Basic Elements of Oracle SQL: Data Types". Oracle Database SQL Language Reference 11g Release two (11.two). Oracle Database Documentation Library. Redwood City, CA: Oracle USA, Inc. Retrieved December 29, 2010. The datetime information types are DATE...
  28. ^ Lorentz, Diana; Roeser, Mary Beth; Abraham, Sundeep; Amor, Angela; Arora, Geeta; Arora, Vikas; Ashdown, Lance; Baer, Hermann; Bellamkonda, Shrikanth (October 2010) [1996]. "Basic Elements of Oracle SQL: Data Types". Oracle Database SQL Language Reference 11g Release two (eleven.2). Oracle Database Documentation Library. Redwood Metropolis, CA: Oracle United states, Inc. Retrieved December 29, 2010. Do not define columns with the following SQL/DS and DB2 data types, because they have no corresponding Oracle data type:... TIME
  29. ^ "Finding Aid". X3H2 Records, 1978–95. American National Standards Institute.
  30. ^ Doll, Shelley (June 19, 2002). "Is SQL a Standard Anymore?". TechRepublic's Builder.com. TechRepublic. Archived from the original on 2012-07-05. Retrieved 2016-04-12 .
  31. ^ a b Gillespie, Patrick. "Pronouncing SQL: S-Q-L or Sequel?". Retrieved 12 Feb 2012.
  32. ^ Melton, Jim; Alan R Simon (1993). "1.2. What is SQL?". Understanding the New SQL: A Complete Guide. Morgan Kaufmann. p. 536. ISBN978-one-55860-245-8. SQL (correctly pronounced "ess cue ell," instead of the somewhat common "sequel")...
  33. ^ a b Wagner, Michael (2010). SQL/XML:2006 - Evaluierung der Standardkonformität ausgewählter Datenbanksysteme. Diplomica Verlag. p. 100. ISBN978-3-8366-9609-eight.
  34. ^ "SQL:2008 at present an approved ISO international standard". Sybase. July 2008. Archived from the original on 2011-06-28.
  35. ^ Krishna Kulkarni, Jan-Eike Michels (September 2012). "Temporal features in SQL:2011" (PDF). SIGMOD Tape. 41 (3).
  36. ^ Fred Zemke (2012). "What's new in SQL:2011" (PDF). Oracle Corporation.
  37. ^ "ISO/IEC 9075-ii:2016: Information technology -- Database languages -- SQL -- Role 2: Foundation (SQL/Foundation)". December 2016.
  38. ^ SQL:2008 draft (Zip), Whitemarsh Information Systems Corporation
  39. ^ "ISO/IEC 9075-1:2016: Information technology – Database languages – SQL – Part ane: Framework (SQL/Framework)".
  40. ^ ISO/IEC 9075-11:2008: Information and Definition Schemas (SQL/Schemata)
  41. ^ Fernando Saenz-Perez. "Outer Joins in a Deductive Database System" (PDF). Lbd.udc.es . Retrieved 2017-01-16 .
  42. ^ Reinsch, R. (1988). "Distributed database for SAA". IBM Systems Periodical. 27 (3): 362–389. doi:10.1147/sj.273.0362.
  43. ^ Distributed Relational Database Architecture Reference. IBM Corp. SC26-4651-0. 1990.
  44. ^ Brandon, Jamie (July 2021). "Against SQL". Retrieved 2 Baronial 2021.
  45. ^ Schauder, Jen. "Why SQL Sucks". Schauderhaft . Retrieved three Feb 2018.

Sources [edit]

  • Codd, Edgar F (June 1970). "A Relational Model of Data for Large Shared Data Banks". Communications of the ACM. xiii (6): 377–87. doi:10.1145/362384.362685. S2CID 207549016. Archived from the original on 2007-06-12.
  • Word 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 linguistic communication SQL, fourth ed., Addison Wesley, USA 1997, ISBN 978-0-201-96426-4

SQL standards documents [edit]

ITTF publicly available standards and technical reports [edit]

The ISO/IEC Information technology Task Force publishes publicly available standards including SQL. Technical Corrigenda (corrections) and Technical Reports (give-and-take documents) are published in that location.

SQL -- Function 1: Framework (SQL/Framework)

Draft documents [edit]

Formal SQL standards are available from ISO and ANSI for a fee. For informative use, as opposed to strict standards compliance, belatedly drafts often suffice.

  • SQL:2011 draft
  • SQL-92 draft

External links [edit]

  • 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 Establish. 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 piece of work on relational database technology. Chamberlin was a member of the Organisation R research team and, with Raymond F. Boyce, adult the SQL database linguistic communication. Chamberlin too briefly discusses his more contempo 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 lawmaking 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 existent-time processing of streaming data with continuous SQL queries
  • BNF Grammar for ISO/IEC 9075:2003, part 2 SQL/Framework

What Is Sql Database Used For,

Source: https://en.wikipedia.org/wiki/SQL

Posted by: hansonlins1970.blogspot.com

0 Response to "What Is Sql Database Used For"

Post a Comment

Subscribe to: Post Comments (Atom)

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel