SQL Aliases
Explained for Beginners

SQL queries can quickly become messy.

That is where SQL aliases help. Aliases make SQL queries easier to read, easier to write, and much easier to understand. If you are learning SQL for data analysis, aliases are a practical skill you will use constantly.

This is one of those “small concept, huge usefulness” SQL topics.

A SQL alias is a temporary name given to a column or table. It makes query output cleaner and query writing simpler.

SELECT revenue AS total_revenue
FROM orders;

Analysts rarely work with perfectly named columns. Real databases often look like this: cust_id, txn_amt, usr_created_dt, acct_stat_cd. Not ideal.

Or worse: customer_transaction_revenue_monthly_adjusted_net. That becomes painful.

SELECT customer_transaction_revenue_monthly_adjusted_net AS net_revenue
FROM orders;

Aliases are a professional habit.

Column aliases rename output columns.

SELECT customer_name AS name
FROM customers;

Original database column remains: customer_name. Only output changes.

Alias Syntax

-- Standard syntax:
SELECT column_name AS alias_name
FROM table_name;

-- Example:
SELECT revenue AS total_sales
FROM orders;

Is AS Required?

Usually no. You could write: SELECT revenue total_sales FROM orders;. But best practice: Use AS. Why? Because it improves readability. Especially for beginners and teams.

This is where aliases become extremely useful.

-- Without alias:
SELECT quantity * unit_price
FROM order_items;

-- Better (With alias):
SELECT quantity * unit_price AS total_order_value
FROM order_items;

Aliases with Aggregate Functions

Aggregations without aliases look ugly. SELECT SUM(revenue) might output a column named sum.

SELECT SUM(revenue) AS total_revenue
FROM orders;

SELECT COUNT(*) AS customer_count
FROM customers;

SELECT AVG(order_value) AS avg_order_value
FROM orders;

Table aliases rename tables temporarily. This makes long queries easier to write.

-- Without alias:
SELECT customers.customer_name
FROM customers;

-- Better:
SELECT c.customer_name
FROM customers AS c;

Why Table Aliases Matter

Especially useful in joins.

-- Without aliases (ugly):
SELECT customers.customer_name, orders.order_id
FROM customers
INNER JOIN orders
ON customers.customer_id = orders.customer_id;

-- Cleaner version:
SELECT c.customer_name, o.order_id
FROM customers AS c
INNER JOIN orders AS o
ON c.customer_id = o.customer_id;

You can create user-friendly output labels using quotes.

SELECT revenue AS "Monthly Revenue"
FROM orders;

But for code-heavy workflows: Cleaner snake_case aliases are better. monthly_revenue is better than "Monthly Revenue".

Alias Scope

Aliases only exist inside the query. This is temporary naming.

1. Rename salary as employee_salary.
2. Alias customers as c.
3. Name a calculated field (quantity * price).
4. Alias an aggregate (COUNT(*)).

What Comes Next?

Now that queries are easier to read, next comes SQL comments. Because readable SQL is not just about cleaner names. It is also about documenting logic properly.

SQL aliases are simple. But they dramatically improve query readability.

This is one of the highest ROI SQL habits to build early.