Preamble
In this tutorial you will learn how to use Oracle ALIASES (aliases for columns or tables) with syntax and examples.
Oracle ALIASES can be used to create an alias for a column or table.
ALIASES columns are used to simplify the reading of columns in your resulting set.
ALIASES tables are used to shorten your SQL code to make it easier to read or when you make a standalone connection (i.e.: enumerating the same table more than once in the FROM sentence).
Syntax for ALIAS columns in Oracle / PLSQL
column_name AS alias_name
OR
Syntax for ALIAS tables in Oracle / PLSQL
table_name alias_name
Parameters or arguments
- column_name – the original name of the column to which you want to specify an alias.
- table_name – the initial name of the table to which you want to specify an alias.
- alias_name – the nickname for the destination.
Note: If alias_name contains spaces, you must quote alias_name.
Example of ALIAS as a column
Typically, aliases are used to simplify the reading of column headers in your resulting set. For example, when fields are concatenated, you may get the following result.
For example:
SELECT contact_id, first_name || last_name AS NAME
FROM contacts
WHERE last_name = 'Anderson';
In this example, we replaced the second column (that is: first_name and last_name concatenated) as NAME. The result is that the NAME will appear as the header for the second column when the resulting set is returned.
Since our alias_name contains no spaces, we do not have to wrap alias_name in quotes.
However, it would be acceptable to write this example using quotes as follows:
SELECT contact_id, first_name || last_name AS "NAME"
FROM contacts
WHERE last_name = 'Anderson';
Then let’s take a look at an example where we should quote alias_name.
For instance:
SELECT contact_id, first_name || last_name AS "CONTACT NAME"
FROM contacts
WHERE last_name = 'Anderson';
In this example, we changed the second column (i.e.: first_name and last_name were concatenated) to “CONTACT NAME”. Since there are spaces in this alias, “CONTACT NAME” must be enclosed in quotes.
Example ALIAS table
When you create an alias for a table, this is either because you plan to list the same table name more than once in the FROM sentence (i.e.: join), or you want to shorten the table name to make the SQL statement shorter and easier to read.
Let’s take the example of ALIAS table name in Oracle / PLSQL.
For example:
SELECT p.product_id, p.product_name, categories.category_name
FROM products p
INNER JOIN categories
ON p.category_id = categories.category_id
ORDER BY p.product_name ASC, categories.category_name ASC;
In this example, we created an alias for the products p. table. In this SQL instruction, we can now refer to the products table as p.
When creating table aliases, there is no need to create aliases for all tables listed in the FROM sentence. You can create aliases for any or all tables.
For example, we could change our example above and create an alias for the table in this way.
SELECT p.product_id, p.product_name, c.category_name
FROM products p
INNER JOIN categories c
ON p.category_id = c.category_id
ORDER BY p.product_name ASC, c.category_name ASC;
We now have an alias for the categories c table, and an alias for the products p table.
What are Table Aliases? (Introduction to Oracle SQL)
About Enteros
Enteros offers a patented database performance management SaaS platform. It proactively identifies root causes of complex business-impacting database scalability and performance issues across a growing number of clouds, RDBMS, NoSQL, and machine learning database platforms.
The views expressed on this blog are those of the author and do not necessarily reflect the opinions of Enteros Inc. This blog may contain links to the content of third-party sites. By providing such links, Enteros Inc. does not adopt, guarantee, approve, or endorse the information, views, or products available on such sites.
Are you interested in writing for Enteros’ Blog? Please send us a pitch!
RELATED POSTS
How to Align Retail Revenue Growth with AI SQL and Cloud FinOps Using Enteros
- 24 February 2026
- Database Performance Management
Introduction Retail and ecommerce have entered an era where digital performance directly determines revenue. Every product search, cart update, checkout transaction, loyalty reward calculation, inventory sync, and real-time recommendation is powered by databases running in the cloud. If those databases slow down, over-scale inefficiently, or operate without financial transparency, revenue growth becomes unstable and margins … Continue reading “How to Align Retail Revenue Growth with AI SQL and Cloud FinOps Using Enteros”
How to Modernize Insurance IT with Enteros: Database Optimization and Transparent Cost Attribution
Introduction The insurance industry is undergoing a profound digital transformation. Policyholders expect seamless mobile experiences. Claims must be processed in real time. Underwriting decisions rely on predictive analytics. Regulatory reporting requires complete transparency. At the center of all these demands lies one critical asset: data. From policy administration systems and claims platforms to actuarial models … Continue reading “How to Modernize Insurance IT with Enteros: Database Optimization and Transparent Cost Attribution”
Who Should Use Enteros for RevOps Efficiency: AI-Powered Cost Estimation and Performance Optimization
- 23 February 2026
- Database Performance Management
Introduction Revenue Operations (RevOps) has evolved from a coordination function into a strategic growth engine. Today’s organizations rely on RevOps to unify sales, marketing, customer success, finance, and IT around one common objective: predictable revenue growth. But there’s a hidden challenge most revenue leaders underestimate. Behind every CRM workflow, marketing automation campaign, subscription billing system, … Continue reading “Who Should Use Enteros for RevOps Efficiency: AI-Powered Cost Estimation and Performance Optimization”
How to Achieve Banking Cost Transparency and Database Stability with Enteros AIOps Intelligence
Introduction In today’s banking environment, CIOs are balancing three relentless pressures: regulatory compliance, cost optimization, and uninterrupted digital performance. Core banking systems must process millions of transactions per hour. Digital banking platforms must operate 24/7. Fraud detection engines and risk analytics pipelines must run in real time. And all of it must be cost-efficient, audit-ready, … Continue reading “How to Achieve Banking Cost Transparency and Database Stability with Enteros AIOps Intelligence”