Query execution plans in DBMS Theory - Step-by-Step Execution

Concept Flow - Query execution plans

Start: Receive SQL Query

↓

Parse Query Syntax

↓

Generate Logical Plan

↓

Optimize Logical Plan

↓

Generate Physical Plan

↓

Execute Plan Steps

↓

Return Query Result

The database receives a SQL query, parses it, creates a logical plan, optimizes it, generates a physical plan, executes it step-by-step, and returns the result.

Execution Sample

DBMS Theory

SELECT name FROM employees WHERE age > 30;

This query selects employee names where their age is greater than 30.

Analysis Table

Step	Action	Details	Result
1	Parse Query	Check syntax of SELECT name FROM employees WHERE age > 30;	Syntax valid
2	Generate Logical Plan	Create plan: Scan employees table, filter age > 30, project name column	Logical plan created
3	Optimize Plan	Choose best method: Use index on age if available	Optimized plan with index scan
4	Generate Physical Plan	Plan steps: Index scan on age, retrieve name	Physical plan ready
5	Execute Plan	Perform index scan, filter rows, collect names	Rows with age > 30 retrieved
6	Return Result	Send list of names to user	Query result returned

💡 Query execution completes after returning the result set.

State Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	Final
Query	SELECT name FROM employees WHERE age > 30;	Logical plan created	Optimized plan with index scan	Physical plan ready	Rows filtered and collected	Result returned
Plan Type	None	Logical plan	Optimized logical plan	Physical plan	Executing plan	Execution complete

Key Insights - 3 Insights

Why does the database create a logical plan before executing the query?

The logical plan breaks down the query into steps without worrying about how to do them efficiently. This is shown in step 2 of the execution_table where the plan is created before optimization.

What is the purpose of the optimization step in query execution?

Optimization chooses the best way to run the query, like using indexes. Step 3 in the execution_table shows the plan being optimized to improve performance.

Why is there a separate physical plan after optimization?

The physical plan details exactly how the database will execute the query on the hardware. Step 4 shows this plan ready for execution, translating the optimized logic into real actions.

Visual Quiz - 3 Questions

Look at the execution_table, what happens at step 3?

A The logical plan is optimized for better performance

B The physical plan is executed

C The query syntax is checked for errors

D The query result is returned

💡 Hint

Refer to the 'Action' and 'Details' columns in step 3 of the execution_table.

At which step does the database actually retrieve data from the table?

A Step 4

B Step 5

C Step 2

D Step 6

💡 Hint

Check the 'Action' column for when the plan is executed and rows are collected.

If the employees table has no index on age, which step would change the most?

A Step 1: Parsing

B Step 5: Execution

C Step 3: Optimization

D Step 6: Returning result

💡 Hint

Look at step 3 where the optimizer chooses the best method; lack of index affects optimization.

Concept Snapshot

Query execution plans break down SQL queries into steps:
1. Parse query syntax
2. Create logical plan (what to do)
3. Optimize plan (best way to do it)
4. Generate physical plan (how to do it)
5. Execute plan steps
6. Return results
This process helps databases run queries efficiently.

Full Transcript

When a database receives a SQL query, it first checks the syntax to ensure it is correct. Then, it creates a logical plan that outlines what steps are needed to get the data. Next, the database optimizes this plan to find the fastest way to run it, such as using indexes. After optimization, a physical plan is made that details exactly how to perform each step on the hardware. The database then executes these steps, retrieves the data, and finally returns the results to the user. This step-by-step process is called the query execution plan and helps the database run queries efficiently and quickly.