Tables, rows, and columns concept in SQL - Time & Space Complexity

Time Complexity: Tables, rows, and columns concept

O(n)

Understanding Time Complexity

When working with tables in a database, it is important to understand how the time to access data grows as the table gets bigger.

We want to know how the number of rows and columns affects the time it takes to find or process data.

Scenario Under Consideration

Analyze the time complexity of the following SQL query.

SELECT *
FROM Employees
WHERE Department = 'Sales';
    

This query searches the Employees table for all rows where the Department column equals 'Sales'.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Checking each row in the Employees table to see if the Department matches 'Sales'.
• How many times: Once for every row in the table.

How Execution Grows With Input

As the number of rows grows, the database must check more rows one by one.

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

Pattern observation: The number of operations grows directly with the number of rows.

Final Time Complexity

Time Complexity: O(n)

This means the time to find matching rows grows in a straight line as the table gets bigger.

Common Mistake

[X] Wrong: "Adding more columns will make the query slower in the same way as adding more rows."

[OK] Correct: The query time mainly depends on how many rows are checked, not how many columns each row has.

Interview Connect

Understanding how table size affects query time helps you explain database performance clearly and confidently.

Self-Check

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

Practice

1. What does a row represent in a database table?

easy

A. A group of tables linked together

B. The name of the table

C. The type of data stored in the table

D. A single record containing data for each column

Solution

1. Step 1: Understand the structure of a table

   A table is made up of rows and columns where columns define data types and rows hold data.

2. Step 2: Identify what a row represents

   A row is one complete record with values for each column in the table.

3. Final Answer:

   A single record containing data for each column -> Option D

4. Quick Check:

   Row = single record [OK]

Hint: Rows = records, columns = data types [OK]

Common Mistakes:

• Confusing rows with columns
• Thinking rows are table names
• Mixing up rows with database schemas

2. Which of the following is the correct way to select all columns from a table named Employees?

easy

A. GET * FROM Employees;

B. SELECT ALL COLUMNS Employees;

C. SELECT * FROM Employees;

D. SELECT COLUMNS FROM Employees;

Solution

1. Step 1: Recall SQL syntax for selecting all columns

   The standard SQL command to select all columns is SELECT * FROM table_name;.

2. Step 2: Match the correct syntax

   SELECT * FROM Employees; matches the correct syntax exactly.

3. Final Answer:

   SELECT * FROM Employees; -> Option C

4. Quick Check:

   SELECT * = all columns [OK]

Hint: Use * to select all columns [OK]

Common Mistakes:

• Using GET instead of SELECT
• Writing SELECT ALL COLUMNS which is invalid
• Omitting FROM keyword

3. Given the table Students with columns id, name, and age, what will this query return?

SELECT name FROM Students WHERE age > 20;

medium

A. Only the names of students older than 20

B. All columns for students older than 20

C. Only the ages of students older than 20

D. An error because age is not selected

Solution

1. Step 1: Analyze the SELECT clause

   The query selects only the name column from the table.

2. Step 2: Analyze the WHERE condition

   It filters rows where age is greater than 20, so only those students are included.

3. Final Answer:

   Only the names of students older than 20 -> Option A

4. Quick Check:

   SELECT name WHERE age > 20 = names only [OK]

Hint: SELECT columns control output, WHERE filters rows [OK]

Common Mistakes:

• Thinking all columns are returned
• Assuming age column is returned without selecting it
• Believing query causes error due to WHERE clause

4. What is wrong with this SQL query?

SELECT id, name FROM Students WHERE age = 'twenty';

medium

A. Using quotes around a number in WHERE clause causes error

B. Comparing age to a string 'twenty' may cause no matches

C. Selecting multiple columns requires commas

D. Missing FROM keyword before table name

Solution

1. Step 1: Check the WHERE clause comparison

   The query compares age to the string 'twenty', but age is numeric.

2. Step 2: Understand effect of comparing number to string

   This will not cause a syntax error but likely returns zero rows because no numeric age equals 'twenty'.

3. Final Answer:

   Comparing age to a string 'twenty' may cause no matches -> Option B

4. Quick Check:

   Wrong data type comparison = no results [OK]

Hint: Match data types in WHERE clause [OK]

Common Mistakes:

• Thinking quotes cause syntax error
• Assuming query returns matching rows
• Ignoring data type mismatch

5. You have a table Orders with columns order_id, customer_id, and amount. You want to find the total amount spent by each customer. Which SQL query correctly groups and sums the data?

hard

A. SELECT customer_id, SUM(amount) FROM Orders GROUP BY customer_id;

B. SELECT order_id, SUM(amount) FROM Orders GROUP BY order_id;

C. SELECT customer_id, amount FROM Orders WHERE SUM(amount) > 100;

D. SELECT customer_id, amount FROM Orders GROUP BY amount;

Solution

1. Step 1: Identify the goal

   We want total amount spent per customer, so we must group by customer_id.

2. Step 2: Use aggregation function

   SUM(amount) calculates total amount per group.

3. Step 3: Check query correctness

   SELECT customer_id, SUM(amount) FROM Orders GROUP BY customer_id; correctly groups by customer_id and sums amount.

4. Final Answer:

   SELECT customer_id, SUM(amount) FROM Orders GROUP BY customer_id; -> Option A

5. Quick Check:

   Group by customer_id + SUM(amount) = total per customer [OK]

Hint: Group by key, aggregate values with SUM [OK]

Common Mistakes:

• Grouping by wrong column
• Using WHERE with aggregate functions incorrectly
• Selecting columns not in GROUP BY without aggregation