Fraud Blocker
  • Solution
    • Solution
      • Enteros UpBeat: Autonomous Intelligence for Complex Production Systems
      • Enteros – Expert Services
    • ROI
      • ROI Calculator
    • Use Cases
      • DevOps
      • Monitoring Business Performance
      • IT Operations Database Intelligence
      • Cloud Migration and Scaling
      • Continuous Delivery
      • NoSQL / MongoDB / Cassandra
    • Industries
      • Healthcare
      • Financial Services
      • Retail
      • Insurance
      • Telecom
      • Government
      • Social Media & Entertainment
    • Roles
      • CIO/CTO Operations Intelligence
      • CFO
      • CRO
      • Engineering Management
      • DevOps Operations Manager
  • Product
    • UpBeat
      • Technical capabilities
      • FinOps and Capacity Intelligence
    • UpBeat Platform
      • FinOps and Capacity Intelligence
      • Anomalies and Cost Analyzer
      • Oracle Performance Investigation
      • Oracle Database Diagnostic Evidence and Remediation
      • Database Diagnostic Evidence and Remediation
    • Enterprise database operations architectureA technical position paper on turning operating questions into reviewable, evidence-grounded answers—explicit about uncertainty and separated from authority to change production systems.
      • Read the architecture paper
  • Company
    •  About
      • Overview
      • Contact Enteros
      • Support
      • Partner with Enteros
      • Careers
      • Enteros News & Perspectives
      • Blog
      • Management
    • Industry recognition and perspectivesArchitecture research, product developments, and dated industry references from Enteros.
      • Explore news and perspectives
    •  
  • Search
  • UpBeat Demo
  • Contact Enteros
(408) 824-1292

Oracle Aliases.

See Live Demo Start Free Trial

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.

Read more"Indian Country" highlights Enteros and its database performance management platform *

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

Read moreInteresting article from OpenAI on scaling kubernetes

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:

Read moreArtificial Intelligence

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 Do Utility Companies Handle Database Performance with Millions of Smart Meter Transactions?

  • 25 September 2026
  • Database Performance Management
  • anomaly detection
  • Cloud FinOps
  • database observability
  • Database Performance
  • Energy and Utilities
  • Enteros UpBeat.
  • root cause analysis
  • Smart Meter Data
  • Smart Meters
  • SQL performance
  • Utility Database Performance Monitoring

Utility companies can keep database performance consistent across millions of smart meter transactions by continuously monitoring SQL workloads, transaction throughput, query latency, storage I/O, database waits, resource utilisation and sudden workload changes. Utility database performance monitoring helps IT teams identify bottlenecks earlier, tune inefficient queries, plan for capacity, and keep smart meter, billing and customer … Continue reading “How Do Utility Companies Handle Database Performance with Millions of Smart Meter Transactions?”

Continue Reading

How to prevent database bottlenecks in smart cities for real-time IoT and citizen services

  • Database Performance Management
  • anomaly detection
  • Citizen Services
  • database observability
  • Database Performance
  • Enteros UpBeat.
  • Government IT
  • IoT Database Performance
  • root cause analysis
  • Smart Cities
  • Smart City Database Performance Monitoring
  • SQL performance

Smart cities can avoid database bottlenecks across their IoT and citizen-facing systems by continuously monitoring SQL workloads, transaction latency, database waits, connection levels, resource usage, API activity, and sudden changes in workload. Effectively monitoring the smart city database performance can help government IT teams identify performance problems sooner, optimise inefficient SQL, manage high-volume data streams … Continue reading “How to prevent database bottlenecks in smart cities for real-time IoT and citizen services”

Continue Reading

How Can eCommerce Brands Prevent Database Slowdowns During Peak Sales?

  • Database Performance Management

    eCommerce brands can protect ecommerce database performance during peak sales by continuously monitoring SQL workloads, transaction latency, CPU, memory, storage I/O, locks, waits, and connection growth. Strong database performance for ecommerce also requires query optimization, historical baselines, anomaly detection, root cause analysis, load testing, and capacity planning before flash sales, holidays, or major promotions begin. … Continue reading “How Can eCommerce Brands Prevent Database Slowdowns During Peak Sales?”

    Continue Reading

    How Logistics Companies Improve Their Databases For Tracking High Volumes of Shipments

    • 24 September 2026
    • Software Engineering
    • anomaly detection
    • API Workloads
    • Cloud FinOps
    • database observability
    • Database Performance
    • Enteros UpBeat.
    • Logistics Database Performance Monitoring
    • root cause analysis
    • Shipment Tracking
    • SQL performance
    • Supply Chain Technology

    During high volume shipment tracking, logistics companies can continuously monitor SQL workloads, transaction latency, database waits, resource utilisation, API activity, locking and sudden changes in workload to maintain database performance. Effective logistics database performance monitoring helps IT teams to identify bottlenecks earlier, optimise inefficient queries, improve system responsiveness and prepare infrastructure for periods of intense … Continue reading “How Logistics Companies Improve Their Databases For Tracking High Volumes of Shipments”

    Continue Reading

    Company

    • Production Database Performance Management
    • Enteros Professional Expert Services
    • NoSQL
    • Contact Us

    Solutions

    • DevOps
    • IT Operations Database Intelligence
    • CFO FinOps Intelligence for Database Spend
    • Engineering Management Database Intelligence
    • Retail Database Operations Intelligence

    UpBeat SaaS

    • Performance Explorer-i – Oracle Database Performance Management
    • High Load Capture – High Precision Database Performance Management
    • DBAct
    • Grid2Go – Advanced Database Analysis
    • Load2Test for Databases

    Resources

    • Verticals
    • Case Studies
    • UpBeat Access
    • UpBeat Documentation
    • Privacy Policy
    • Terms of Service

    Connect with Us

    Copyright © 2026 | Enteros, Inc. All Rights Reserved

    🎉 Thank you for subscribing!

    You're now on the list for database FinOps strategies and performance insights.