Column aliases with AS in SQL - Time & Space Complexity

Time Complexity: Column aliases with AS

O(n)

Understanding Time Complexity

Let's see how the time it takes to run a query with column aliases changes as the data grows.

We want to know how adding aliases affects the work done by the database.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

SELECT employee_id AS id, 
       first_name AS name, 
       salary AS pay
FROM employees;

This query selects three columns from the employees table and renames them using AS.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Reading each row from the employees table.
• How many times: Once for every row in the table.

How Execution Grows With Input

As the number of rows grows, the database reads more rows, but renaming columns is a simple label change.

Input Size (n)	Approx. Operations
10	Reads 10 rows, renames 3 columns each
100	Reads 100 rows, renames 3 columns each
1000	Reads 1000 rows, renames 3 columns each

Pattern observation: The work grows directly with the number of rows; renaming columns adds almost no extra work.

Final Time Complexity

Time Complexity: O(n)

This means the time grows in a straight line with the number of rows in the table.

Common Mistake

[X] Wrong: "Using AS to rename columns makes the query slower because it adds extra work for each row."

[OK] Correct: Renaming columns is just a label change and does not add extra reading or processing per row.

Interview Connect

Understanding how simple query features like column aliases affect performance shows you know what really matters in database work.

Self-Check

"What if we added a WHERE clause filtering rows? How would the time complexity change?"