This article includes a list of general references, but it lacks sufficient corresponding inline citations .(July 2022) |
Set operations in SQL is a type of operations which allow the results of multiple queries to be combined into a single result set. [1]
Set operators in SQL include UNION
, INTERSECT
, and EXCEPT
, which mathematically correspond to the concepts of union, intersection and set difference.
In SQL the UNION
clause combines the results of two SQL queries into a single table of all matching rows. The two queries must result in the same number of columns and compatible data types in order to unite. Any duplicate records are automatically removed unless UNION ALL
is used.
UNION
can be useful in data warehouse applications where tables are not perfectly normalized. [2] A simple example would be a database having tables sales2005
and sales2006
that have identical structures but are separated because of performance considerations. A UNION
query could combine results from both tables.
Note that UNION ALL
does not guarantee the order of rows. Rows from the second operand may appear before, after, or mixed with rows from the first operand. In situations where a specific order is desired, ORDER BY
must be used.
Note that UNION ALL
may be much faster than plain UNION
.
Given these two tables:
person | amount |
---|---|
Joe | 1000 |
Alex | 2000 |
Bob | 5000 |
person | amount |
---|---|
Joe | 2000 |
Alex | 2000 |
Zach | 35000 |
Executing this statement:
SELECT*FROMsales2005UNIONSELECT*FROMsales2006;
yields this result set, though the order of the rows can vary because no ORDER BY
clause was supplied:
person | amount |
---|---|
Joe | 1000 |
Alex | 2000 |
Bob | 5000 |
Joe | 2000 |
Zach | 35000 |
Note that there are two rows for Joe because those rows are distinct across their columns. There is only one row for Alex because those rows are not distinct for both columns.
UNION ALL
gives different results, because it will not eliminate duplicates. Executing this statement:
SELECT*FROMsales2005UNIONALLSELECT*FROMsales2006;
would give these results, again allowing variance for the lack of an ORDER BY
statement:
person | amount |
---|---|
Joe | 1000 |
Joe | 2000 |
Alex | 2000 |
Alex | 2000 |
Bob | 5000 |
Zach | 35000 |
The discussion of full outer joins also has an example that uses UNION
.
The SQL INTERSECT
operator takes the results of two queries and returns only rows that appear in both result sets. For purposes of duplicate removal the INTERSECT
operator does not distinguish between NULLs
. The INTERSECT
operator removes duplicate rows from the final result set. The INTERSECT ALL
operator does not remove duplicate rows from the final result set, but if a row appears X times in the first query and Y times in the second, it will appear times in the result set.
The following example INTERSECT
query returns all rows from the Orders table where Quantity is between 50 and 100.
SELECT*FROMOrdersWHEREQuantityBETWEEN1AND100INTERSECTSELECT*FROMOrdersWHEREQuantityBETWEEN50AND200;
The SQL EXCEPT
operator takes the distinct rows of one query and returns the rows that do not appear in a second result set. For purposes of row elimination and duplicate removal, the EXCEPT
operator does not distinguish between NULLs
. The EXCEPT ALL
operator does not remove duplicates, but if a row appears X times in the first query and Y times in the second, it will appear times in the result set.
Notably, the Oracle platform provides a MINUS
operator which is functionally equivalent to the SQL standard EXCEPT DISTINCT
operator. [3]
The following example EXCEPT
query returns all rows from the Orders table where Quantity is between 1 and 49, and those with a Quantity between 76 and 100.
Worded another way; the query returns all rows where the Quantity is between 1 and 100, apart from rows where the quantity is between 50 and 75.
SELECT*FROMOrdersWHEREQuantityBETWEEN1AND100EXCEPTSELECT*FROMOrdersWHEREQuantityBETWEEN50AND75;
The following example is equivalent to the above example but without using the EXCEPT
operator.
SELECTo1.*FROM(SELECT*FROMOrdersWHEREQuantityBETWEEN1AND100)o1LEFTJOIN(SELECT*FROMOrdersWHEREQuantityBETWEEN50AND75)o2ONo1.id=o2.idWHEREo2.idISNULL
A relational database is a database based on the relational model of data, as proposed by E. F. Codd in 1970. A system used to maintain relational databases is a relational database management system (RDBMS). Many relational database systems are equipped with the option of using SQL for querying and updating the database.
The relational model (RM) is an approach to managing data using a structure and language consistent with first-order predicate logic, first described in 1969 by English computer scientist Edgar F. Codd, where all data is represented in terms of tuples, grouped into relations. A database organized in terms of the relational model is a relational database.
In database theory, relational algebra is a theory that uses algebraic structures for modeling data, and defining queries on it with a well founded semantics. The theory was introduced by Edgar F. Codd.
Online analytical processing, or OLAP, is an approach to answer multi-dimensional analytical (MDA) queries swiftly in computing. OLAP is part of the broader category of business intelligence, which also encompasses relational databases, report writing and data mining. Typical applications of OLAP include business reporting for sales, marketing, management reporting, business process management (BPM), budgeting and forecasting, financial reporting and similar areas, with new applications emerging, such as agriculture.
A join clause in the Structured Query Language (SQL) combines columns from one or more tables into a new table. The operation corresponds to a join operation in relational algebra. Informally, a join stitches two tables and puts on the same row records with matching fields : INNER
, LEFT OUTER
, RIGHT OUTER
, FULL OUTER
and CROSS
.
The SQL SELECT statement returns a result set of records, from one or more tables.
An SQL INSERT statement adds one or more records to any single table in a relational database.
A data manipulation language (DML) is a computer programming language used for adding (inserting), deleting, and modifying (updating) data in a database. A DML is often a sublanguage of a broader database language such as SQL, with the DML comprising some of the operators in the language. Read-only selecting of data is sometimes distinguished as being part of a separate data query language (DQL), but it is closely related and sometimes also considered a component of a DML; some operators may perform both selecting (reading) and writing.
A table is a collection of related data held in a table format within a database. It consists of columns and rows.
A query plan is a sequence of steps used to access data in a SQL relational database management system. This is a specific case of the relational model concept of access plans.
A database index is a data structure that improves the speed of data retrieval operations on a database table at the cost of additional writes and storage space to maintain the index data structure. Indexes are used to quickly locate data without having to search every row in a database table every time said table is accessed. Indexes can be created using one or more columns of a database table, providing the basis for both rapid random lookups and efficient access of ordered records.
In a database, a view is the result set of a stored query, which can be queried in the same manner as a persistent database collection object. This pre-established query command is kept in the data dictionary. Unlike ordinary base tables in a relational database, a view does not form part of the physical schema: as a result set, it is a virtual table computed or collated dynamically from data in the database when access to that view is requested. Changes applied to the data in a relevant underlying table are reflected in the data shown in subsequent invocations of the view.
In SQL, null or NULL is a special marker used to indicate that a data value does not exist in the database. Introduced by the creator of the relational database model, E. F. Codd, SQL null serves to fulfil the requirement that all true relational database management systems (RDBMS) support a representation of "missing information and inapplicable information". Codd also introduced the use of the lowercase Greek omega (ω) symbol to represent null in database theory. In SQL, NULL
is a reserved word used to identify this marker.
A pivot table is a table of grouped values that aggregates the individual items of a more extensive table within one or more discrete categories. This summary might include sums, averages, or other statistics, which the pivot table groups together using a chosen aggregation function applied to the grouped values.
A dimension is a structure that categorizes facts and measures in order to enable users to answer business questions. Commonly used dimensions are people, products, place and time.
Query optimization is a feature of many relational database management systems and other databases such as NoSQL and graph databases. The query optimizer attempts to determine the most efficient way to execute a given query by considering the possible query plans.
A WHERE
clause in SQL specifies that a SQL Data Manipulation Language (DML) statement should only affect rows that meet specified criteria. The criteria are expressed in the form of predicates. WHERE
clauses are not mandatory clauses of SQL DML statements, but can be used to limit the number of rows affected by a SQL DML statement or returned by a query. In brief SQL WHERE clause is used to extract only those results from a SQL statement, such as: SELECT
, INSERT
, UPDATE
, or DELETE
statement.
Language Integrated Query is a Microsoft .NET Framework component that adds native data querying capabilities to .NET languages, originally released as a major part of .NET Framework 3.5 in 2007.
A hierarchical query is a type of SQL query that handles hierarchical model data. They are special cases of more general recursive fixpoint queries, which compute transitive closures.
The syntax of the SQL programming language is defined and maintained by ISO/IEC SC 32 as part of ISO/IEC 9075. This standard is not freely available. Despite the existence of the standard, SQL code is not completely portable among different database systems without adjustments.
UNION ALL
views technique for managing maintenance and performance in your large data warehouse environment ... This UNION ALL
technique has saved many of my clients with issues related to time-sensitive database designs. These databases usually have an extremely volatile current timeframe, month, or day portion and the older data is rarely updated. Using different container DASD allocations, tablespaces, tables, and index definitions, the settings can be tuned for the specific performance considerations for these different volatility levels and update frequency situations." Terabyte Data Warehouse Table Design Choices - Part 2 (accessed on July 25, 2006)EXCEPT DISTINCT
table operator: Use MINUS
instead of EXCEPT DISTINCT
" "Oracle Compliance To Core SQL:2003". Docs.oracle.com. Retrieved 7 July 2022.