Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
455 views

SQLBolt - Learn SQL - SQL Lesson 12 - Order of Execution of A Query

The document outlines the typical order of execution for an SQL query. 1) The FROM and JOIN clauses are executed to determine the working data set. 2) The WHERE clause filters rows. 3) The GROUP BY clause groups rows. 4) The HAVING clause filters grouped rows. 5) Expressions in the SELECT clause are computed. 6) DISTINCT removes duplicate rows. 7) ORDER BY sorts rows. 8) LIMIT and OFFSET trim the result set. The order allows for efficient querying while maintaining flexibility.

Uploaded by

Md Asif Alam
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
455 views

SQLBolt - Learn SQL - SQL Lesson 12 - Order of Execution of A Query

The document outlines the typical order of execution for an SQL query. 1) The FROM and JOIN clauses are executed to determine the working data set. 2) The WHERE clause filters rows. 3) The GROUP BY clause groups rows. 4) The HAVING clause filters grouped rows. 5) Expressions in the SELECT clause are computed. 6) DISTINCT removes duplicate rows. 7) ORDER BY sorts rows. 8) LIMIT and OFFSET trim the result set. The order allows for efficient querying while maintaining flexibility.

Uploaded by

Md Asif Alam
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

4/12/2020 SQLBolt - Learn SQL - SQL Lesson 12: Order of execution of a Query

Query order of execution

1.  FROM  and  JOIN s

The  FROM  clause, and subsequent  JOIN s are rst executed to determine the total working set of
data that is being queried. This includes subqueries in this clause, and can cause temporary tables to
be created under the hood containing all the columns and rows of the tables being joined.

2.  WHERE

Once we have the total working set of data, the rst-pass  WHERE  constraints are applied to the
individual rows, and rows that do not satisfy the constraint are discarded. Each of the constraints can
only access columns directly from the tables requested in the  FROM  clause. Aliases in
the SELECT  part of the query are not accessible in most databases since they may include
expressions dependent on parts of the query that have not yet executed.

3.  GROUP BY

The remaining rows after the  WHERE  constraints are applied are then grouped based on common
values in the column speci ed in the  GROUP BY  clause. As a result of the grouping, there will only
be as many rows as there are unique values in that column. Implicitly, this means that you should
only need to use this when you have aggregate functions in your query.

4.  HAVING

If the query has a  GROUP BY  clause, then the constraints in the  HAVING  clause are then applied to
the grouped rows, discard the grouped rows that don't satisfy the constraint. Like the  WHERE clause,
aliases are also not accessible from this step in most databases.

5.  SELECT

Any expressions in the  SELECT  part of the query are nally computed.

6.  DISTINCT

Of the remaining rows, rows with duplicate values in the column marked as  DISTINCT  will be
discarded.

7.  ORDER BY

If an order is speci ed by the  ORDER BY  clause, the rows are then sorted by the speci ed data in
either ascending or descending order. Since all the expressions in the  SELECT  part of the query have
been computed, you can reference aliases in this clause.

https://sqlbolt.com/lesson/select_queries_order_of_execution 1/2
4/12/2020 SQLBolt - Learn SQL - SQL Lesson 12: Order of execution of a Query

8.  LIMIT  /  OFFSET

Finally, the rows that fall outside the range speci ed by the  LIMIT  and  OFFSET  are discarded,
leaving the nal set of rows to be returned from the query.

Conclusion

Not every query needs to have all the parts we listed above, but a part of why SQL is so exible is that
it allows developers and data analysts to quickly manipulate data without having to write additional
code, all just by using the above clauses.

https://sqlbolt.com/lesson/select_queries_order_of_execution 2/2

You might also like