A SQL subquery can look complicated:
The core concept to grasp is that the subquery (the part highlighted in blue inside the parentheses) is a separate SQL query that produces a table that is then used in the main query.
Let’s break the example above up and do the subquery first by itself.
This subquery produces a table:
This table from the subquery can then be used by the main query.
Now while this was a somewhat pointless subquery example since you could have just run the subquery to get the same result, it illustrates the point the the outer query is pulling from the created table of the subquery. In this case it is selecting everything from the subquery.
Subqueries are most commonly in the FROM statement as a table to query from. However a subquery can also be placed in the WHERE or HAVING statement. When using it in the WHERE or HAVING statement, the subquery has to produce a single value table if you are using comparison operators such as =, <, <=, >, >=, !=.
Single value subquery table:
Multi-value subquery tables will result in an error since it would try to compare a single field to every row in a column or every cell within table at once.
Multi-value subquery tables can be used with logical operators such as IN which compares a single field to every row in a column or table.
Subqueries can also be written in a WITH statement instead of in the main query. You write WITH and then what you want to name the resulting table from the subquery and then in parentheses write the subquery. Then you can write a query that uses that subquery by referring to the name given to it. When written in this way they are referred to as a common table expression (CTE). Look at the original example and re-written version using a WITH statement below.
Subquery in the Query:
Subquery in a WITH statement:
Writing it this way can help make it more clear that you are first creating a table and then referencing it in the outer query.