How SQL communicates with the database engine - Performance & Efficiency

Time Complexity: How SQL communicates with the database engine

O(n)

Understanding Time Complexity

When SQL sends a command to the database engine, it asks the engine to find or change data. Understanding how long this takes helps us know how well the database will work as data grows.

We want to know: How does the time to run a SQL query change when the data gets bigger?

Scenario Under Consideration

Analyze the time complexity of the following SQL query.

SELECT *
FROM employees
WHERE department_id = 5;
    

This query asks the database to find all employees who work in department number 5.

Identify Repeating Operations

Look at what repeats when the database runs this query.

• Primary operation: Checking each employee record to see if their department matches 5.
• How many times: Once for every employee in the table.

How Execution Grows With Input

As the number of employees grows, the work to check each one grows too.

Input Size (n)	Approx. Operations
10	10 checks
100	100 checks
1000	1000 checks

Pattern observation: The number of checks grows directly with the number of employees.

Final Time Complexity

Time Complexity: O(n)

This means the time to run the query grows in a straight line as the number of records grows.

Common Mistake

[X] Wrong: "The query time stays the same no matter how many records there are."

[OK] Correct: The database must check each record unless it uses special shortcuts like indexes, so more records usually mean more work.

Interview Connect

Knowing how SQL queries grow with data size helps you explain how databases handle large amounts of data. This skill shows you understand what happens behind the scenes.

Self-Check

"What if we added an index on department_id? How would the time complexity change?"

Practice

1. What is the main role of SQL when working with a database engine?

easy

A. To store data physically on the disk

B. To send instructions that the database engine executes

C. To design the hardware of the database server

D. To create user interfaces for database applications

Solution

1. Step 1: Understand SQL's purpose

   SQL is a language used to communicate commands to the database engine.

2. Step 2: Identify the database engine's role

   The database engine executes these commands to manage data.

3. Final Answer:

   To send instructions that the database engine executes -> Option B

4. Quick Check:

   SQL sends instructions = A [OK]

Hint: SQL sends commands to the engine, not hardware or UI [OK]

Common Mistakes:

• Confusing SQL with physical data storage
• Thinking SQL designs hardware
• Assuming SQL creates user interfaces

2. Which of the following is the correct way to write a SQL command to select all columns from a table named users?

easy

A. SELECT * FROM users;

B. GET ALL FROM users;

C. SHOW * FROM users;

D. FETCH ALL users;

Solution

1. Step 1: Recall SQL SELECT syntax

   The correct syntax to get all columns is SELECT * FROM table_name;.

2. Step 2: Match syntax to options

   Only SELECT * FROM users; matches the correct SQL syntax.

3. Final Answer:

   SELECT * FROM users; -> Option A

4. Quick Check:

   Correct SELECT syntax = B [OK]

Hint: Use SELECT * FROM table; to get all columns [OK]

Common Mistakes:

• Using non-SQL keywords like GET or FETCH
• Omitting FROM keyword
• Using SHOW incorrectly

3. Given the table employees with columns id, name, and salary, what will this SQL query return?

SELECT name FROM employees WHERE salary > 50000;

medium

A. Syntax error due to incorrect WHERE clause

B. All columns of employees earning more than 50000

C. Names of employees earning less than 50000

D. Names of employees earning more than 50000

Solution

1. Step 1: Analyze the SELECT clause

   The query selects only the name column.

2. Step 2: Analyze the WHERE condition

   It filters rows where salary > 50000, so only employees earning more than 50000 are included.

3. Final Answer:

   Names of employees earning more than 50000 -> Option D

4. Quick Check:

   SELECT name with salary > 50000 = D [OK]

Hint: WHERE filters rows; SELECT chooses columns [OK]

Common Mistakes:

• Confusing column selection with all columns
• Misreading > as <
• Thinking WHERE causes syntax error

4. Identify the error in this SQL query:

SELEC name FROM customers;

medium

A. Table name is incorrect

B. Missing FROM keyword

C. Misspelled SELECT keyword

D. No error, query is correct

Solution

1. Step 1: Check SQL keywords

   The keyword SELECT is misspelled as SELEC.

2. Step 2: Verify other parts

   The FROM keyword and table name customers are correct.

3. Final Answer:

   Misspelled SELECT keyword -> Option C

4. Quick Check:

   Keyword spelling error = C [OK]

Hint: Check spelling of SQL keywords carefully [OK]

Common Mistakes:

• Ignoring small typos in keywords
• Assuming table name is wrong without checking
• Thinking missing FROM when it is present

5. You want to get the total number of rows in the orders table. Which SQL command correctly communicates this request to the database engine?

hard

A. SELECT COUNT(*) FROM orders;

B. COUNT * FROM orders;

C. GET TOTAL orders;

D. SELECT TOTAL FROM orders;

Solution

1. Step 1: Recall aggregate function syntax

   To count rows, use SELECT COUNT(*) FROM table;.

2. Step 2: Match options to correct syntax

   Only SELECT COUNT(*) FROM orders; uses the correct SQL syntax with SELECT and COUNT(*).

3. Final Answer:

   SELECT COUNT(*) FROM orders; -> Option A

4. Quick Check:

   Correct COUNT syntax = A [OK]

Hint: Use SELECT COUNT(*) FROM table; to count rows [OK]

Common Mistakes:

• Omitting SELECT keyword
• Using non-SQL commands like GET or TOTAL
• Misplacing COUNT function