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 Can Telecom Companies Prevent Database Bottlenecks During Mass Service Activations and Provisioning Events?
- 23 September 2026
- Database Performance Management
Telecom companies can avoid database bottlenecks during mass service activations by monitoring SQL performance, provisioning transactions, database waits, locking, resource utilisation, workload spikes and application dependencies. Good telecom service provisioning database performance management allows teams to identify bottlenecks earlier, tune high-impact queries, plan capacity more intelligently, and keep activation workflows humming along during periods of … Continue reading “How Can Telecom Companies Prevent Database Bottlenecks During Mass Service Activations and Provisioning Events?”
How Can Real Estate Platforms Prevent Database Slowdowns During High-Volume Property Searches and Listing Updates?
By continuously monitoring SQL performance, property-search workloads, listing updates, database waits, resource utilisation and unusual workload changes, real estate platforms can avoid database slowdowns. Effective real estate database performance monitoring enables technology teams to identify bottlenecks sooner, optimise high-impact queries, enhance database observability and sustain responsive property search and listing experiences during periods of heavy … Continue reading “How Can Real Estate Platforms Prevent Database Slowdowns During High-Volume Property Searches and Listing Updates?”
How Can Retail IT Teams Improve Database Capacity Planning for Peak Demand?
- 22 September 2026
- Database Performance Management
Retail IT teams can improve retail database capacity planning by analyzing historical workloads, monitoring SQL performance, tracking CPU, memory, storage, connections, and transaction growth, and forecasting future demand. Strong retail database performance management helps teams identify capacity risks before peak events, while Enteros supports proactive planning with observability, anomaly detection, predictive analytics, and workload intelligence. … Continue reading “How Can Retail IT Teams Improve Database Capacity Planning for Peak Demand?”
How Can Telecom Providers Improve Database Scalability for 5G and IoT Growth?
By integrating SQL optimisation, continuous observability, workload monitoring, anomaly detection, capacity planning, and effective cloud resource management, telecom operators can increase the scalability of telecom databases. Infrastructure that can manage quickly increasing device and transaction loads is necessary for robust database performance for 5G networks. Enteros assists telecom teams with capacity forecasting, bottleneck identification, and … Continue reading “How Can Telecom Providers Improve Database Scalability for 5G and IoT Growth?”