SQL Column Aliases (AS)
Rename a column in the output only — the underlying table is never touched.
What & Why
AS renames a column (or a computed expression) in the query's result, without changing anything about the real table. It's purely cosmetic for the output you see.
See How It Works
| id | name | channel | spend | start_date | end_date | status | target_segment |
|---|---|---|---|---|---|---|---|
| 1 | Spring Launch | google_ads | 55000.00 | 2024-01-15 | 2024-03-31 | active | smb |
| 2 | Retention Webinar | 45000.00 | 2024-02-10 | 2024-04-15 | active | enterprise | |
| 3 | Finance Retargeting | 50000.00 | 2024-03-12 | 2024-05-31 | active | enterprise | |
| 4 | Enterprise Search | google_ads | 60000.00 | 2024-04-01 | 2024-06-30 | active | enterprise |
EXAMPLE QUERY
SELECT name AS campaign_name, spend AS campaign_spend
FROM marketing.campaigns;RESULT — column names changed, data didn't
| campaign_name | campaign_spend |
|---|---|
| Spring Launch | 55000.00 |
| Retention Webinar | 45000.00 |
| Finance Retargeting | 50000.00 |
| Enterprise Search | 60000.00 |
The result uses the same Queryflo columns shown in the worked example.
Now You Try
Practice this concept
Marketing wants campaign names and spend values returned with report-friendly column aliases.
Available schema
marketingPrefix tables with marketing.table_name.
campaign_namecampaign_spendmarketing.campaigns| Column | Type |
|---|---|
| id | integer |
| name | text |
| channel | text |
| spend | numeric |
| start_date | date |
| end_date | date |
| status | text |
| target_segment | text |
| legacy_id | text |
query.sql
Sign up free to try it on a real business scenario