A SELECT statement retrieves zero or more rows from one or more database tables or database views. In most applications,
SELECT is the most commonly used data manipulation language (DML) command. As SQL is a declarative programming language,
SELECT queries specify a result set, but do not specify how to calculate it. The database translates the query into a "query plan" which may vary between executions, database versions and database software. This functionality is called the "query optimizer" as it is responsible for finding the best possible execution plan for the query, within applicable constraints.
The SELECT statement has many optional clauses:
WHEREspecifies which rows to retrieve.
GROUP BYgroups rows sharing a property so that an aggregate function can be applied to each group.
HAVINGselects among the groups defined by the GROUP BY clause.
ORDER BYspecifies an order in which to return the rows.
ASprovides an alias which can be used to temporarily rename tables or columns.
Given a table T, the query
SELECT * FROM T will result in all the elements of all the rows of the table being shown.
With the same table, the query
SELECT C1 FROM T will result in the elements from the column C1 of all the rows of the table being shown. This is similar to a projection in Relational algebra, except that in the general case, the result may contain duplicate rows. This is also known as a Vertical Partition in some database terms, restricting query output to view only specified fields or columns.
With the same table, the query
SELECT * FROM T WHERE C1 = 1 will result in all the elements of all the rows where the value of column C1 is '1' being shown — in Relational algebra terms, a selection will be performed, because of the WHERE clause. This is also known as a Horizontal Partition, restricting rows output by a query according to specified conditions.
With more than one table, the result set will be every combination of rows. So if two tables are T1 and T2,
SELECT * FROM T1, T2 will result in every combination of T1 rows with every T2 rows. E.g., if T1 has 3 rows and T2 has 5 rows, then 15 rows will result.
The SELECT clause specifies a list of properties (columns) by name, or the wildcard character (“*”) to mean “all properties”. Notice the special case of joinpropname, this provides for joins, but only on the jcr:path column, as described in 8.5.2 Database View. See also 126.96.36.199 Column Specifier.
Limiting result rows
Often it is convenient to indicate a maximum number of rows that are returned. This can be used for testing or to prevent consuming excessive resources if the query returns more information than expected. The approach to do this often varies per vendor.
- cursors, or
- By introducing SQL window function to the SELECT-statement
ISO SQL:2008 introduced the
FETCH FIRST clause.
ROW_NUMBER() window function
ROW_NUMBER() OVER may be used for a simple table on the returned rows, e.g. to return no more than ten rows:
SELECT * FROM ( SELECT ROW_NUMBER() OVER (ORDER BY sort_key ASC) AS row_number, columns FROM tablename ) AS foo WHERE row_number <= 11
ROW_NUMBER can be non-deterministic: if sort_key is not unique, each time you run the query it is possible to get different row numbers assigned to any rows where sort_key is the same. When sort_key is unique, each row will always get a unique row number.
RANK() window function
RANK() OVER window function acts like ROW_NUMBER, but may return more than n rows in case of tie conditions, e.g. to return the top-10 youngest persons:
SELECT * FROM ( SELECT RANK() OVER (ORDER BY age ASC) AS ranking, person_id, person_name, age FROM person )AS foo WHERE ranking <= 10
The above code could return more than ten rows, e.g. if there are two people of the same age, it could return eleven rows.
FETCH FIRST clause
Since ISO SQL:2008 results limits can be specified as in the following example using the
FETCH FIRST clause.
SELECT * FROM T FETCH FIRST 10 ROWS ONLY
This clause currently is supported by CA DATACOM/DB 11,IBM DB2, Sybase SQL Anywhere, PostgreSQL, EffiProz, H2, HSQLDB version 2.0, Microsoft SQL Server 2012 and Oracle 12c.
Microsoft SQL Server 2014 requires more:
SELECT * FROM atable ORDER BY acolumn DESC OFFSET 0 ROWS FETCH FIRST 10 ROWS ONLY
Not all DBMSs support the mentioned window functions, and non-standard syntax has to be used. Below, variants of the simple limit query for different DBMSes are listed:
SET ROWCOUNT 10 SELECT * FROM T
|MS SQL Server (This also works on Microsoft SQL Server 6.5 while the Select top 10 * from T does not)|
||Netezza, MySQL, Sybase SQL Anywhere, PostgreSQL (also supports the standard, since version 8.4), SQLite, HSQLDB, H2, Vertica, Polyhedra|
||Informix (row numbers are filtered after order by is evaluated. SKIP clause was introduced in a v10.00.xC4 fixpack)|
||MS SQL Server, Sybase ASE, MS Access, Sybase IQ, Teradata|
||Sybase SQL Anywhere (also supports the standard, since version 9.0.1)|
||Firebird (since version 2.1)|
SELECT * FROM T WHERE ID_T > 10 FETCH FIRST 10 ROWS ONLY
SELECT * FROM T WHERE ID_T > 20 FETCH FIRST 10 ROWS ONLY
|DB2 (new rows are filtered after comparing with key column of table T)|
sum(population) OVER( PARTITION BY city )
calculates the sum of the populations of all rows having the same city value as the current row.
Partitions are specified using the OVER clause which modifies the aggregate. Syntax:
<OVER_CLAUSE> :: = OVER ( [ PARTITION BY <expr>, ... ] [ ORDER BY <expression> ] )
The OVER clause can partition and order the result set. Ordering is used for order-relative functions such as row_number.
Query evaluation ANSI
The processing of a SELECT statement according to ANSI SQL would be the following:
select g.* from users u inner join groups g on g.Userid = u.Userid where u.LastName = 'Smith' and u.FirstName = 'John'
- the FROM clause is evaluated, a cross join or Cartesian product is produced for the first two tables in the FROM clause resulting in a virtual table as Vtable1
- the ON clause is evaluated for vtable1; only records which meet the join condition g.Userid = u.Userid are inserted into Vtable2
- If an outer join is specified, records which were dropped from vTable2 are added into VTable 3, for instance if the above query were:
select u.* from users u left join groups g on g.Userid = u.Userid where u.LastName = 'Smith' and u.FirstName = 'John'
- the WHERE clause is evaluated, in this case only group information for user John Smith would be added to vTable4
- the GROUP BY is evaluated; if the above query were:
select g.GroupName, count(g.*) as NumberOfMembers from users u inner join groups g on g.Userid = u.Userid group by GroupName
- the HAVING clause is evaluated for groups for which the HAVING clause is true and inserted into vTable6. For example:
select g.GroupName, count(g.*) as NumberOfMembers from users u inner join groups g on g.Userid = u.Userid group by GroupName having count(g.*) > 5
- the SELECT list is evaluated and returned as Vtable 7
- the DISTINCT clause is evaluated; duplicate rows are removed and returned as Vtable 8
- the ORDER BY clause is evaluated, ordering the rows and returning VCursor9. This is a cursor and not a table because ANSI defines a cursor as an ordered set of rows (not relational).
Generating Data in T-SQL
Method to generate data based on the union all
select 1 a, 1 b union all select 1, 2 union all select 1, 3 union all select 2, 1 union all select 5, 1
SQL Server 2008 supports the "row constructor" specified in the SQL3 ("SQL:1999") standard
select * from (values (1, 1), (1, 2), (1, 3), (2, 1), (5, 1)) as x(a, b)
- Horizontal & Vertical Partitioning, Microsoft SQL Server 2000 Books Online
- Windowed Tables and Window function in SQL, Stefan Deßloch
- Oracle SELECT Syntax.
- Firebird SELECT Syntax.
- Mysql SELECT Syntax.
- Postgres SELECT Syntax.
- SQLite SELECT Syntax.