Preamble
The Oracle/PLSQL AVG function returns the average value of the expression.
Oracle/PLSQL syntax of AVG function
SELECT AVG(aggregate_expression_id)
FROM tabs
[WHERE conds]
OR AVG function syntax with results grouped by one or more columns:
SELECT expression1_id, expression2_id, ... expression_n_id,
AVG(aggregate_expression_id)
FROM tabs
[WHERE conds]
GROUP BY expression1_id, expression2_id, ... expression_n_id;
Parameters and arguments of the function
- expression1_id, expression2_id, … expression_n_id – Expressions that are not encapsulated in the AVG function must be included in the GROUP BY operator at the end of the SQL sentence.
- aggregate_expression_id – is a column or expression to be averaged.
- tabs – tables from which you want to get records. At least one table must be specified in FROM sentence.
- WHERE conds – are optional. These are the conditions that must be met for the selected records.
The AVG function returns a numeric value.
The AVG function can be used in the following Oracle/PLSQL versions
|
Oracle 12c, Oracle 11g, Oracle 10g, Oracle 9i, Oracle 8i
|
One Field Example
Let’s consider some examples of the AVG function and learn how to use the AVG function in Oracle/PLSQL.
For example, you can find out what is the average salary of all employees whose salary exceeds $18000 per year.
SELECT AVG(salary_id) AS "Avg Salary"
FROM empls
WHERE salary_id > 18,000;
In this example of the AVG function, we called the expression AVG(salary_id) as “Avg Salary”. As a result, “Avg Salary” will be displayed as the field name when the resulting set is returned.
Example – using DISTINCT
You can use DISTINCT operator in AVG function. For example, the following SQL statement returns the average salary with unique values of salary, where the salary exceeds $18000 per year.
In the example below, the average salary of employees from the empls table is calculated.
SELECT AVG(DISTINCT salary_id) AS "Avg Salary"
FROM empls
WHERE salary_id > 18,000;
Example – using formula
The expression contained in the AVG function does not have to be a single field. You can also use a formula. For example, you may need an average commission.
SELECT AVG(sales * 0.10) AS "Average Commission"
FROM ords;
Example – using GROUP BY
You can also use the AVG function to get the department name and average sales (in the corresponding department). For example.
SELECT depart, AVG(sales_id) AS "Avg sales".
FROM ord_details
GROUP BY depart;
Since your SELECT operator has one column that is not encapsulated in the AVG function, you must use GROUP BY. Therefore, the department field must be specified in the GROUP BY operator.
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
From Performance to Profitability: Enteros Database Intelligence for Real Estate Enterprises
- 8 February 2026
- Database Performance Management
Introduction The real estate sector has undergone a dramatic transformation over the past decade. What was once an asset-heavy, relationship-driven industry is now deeply digital, data-intensive, and platform-centric. Property listing portals, smart building platforms, tenant experience apps, valuation engines, AI-driven pricing models, IoT-enabled facilities management systems, and digital transaction platforms all rely on complex, always-on … Continue reading “From Performance to Profitability: Enteros Database Intelligence for Real Estate Enterprises”
Running Retail on Data: How Enteros Transforms Database Performance Management
Introduction Retail has evolved far beyond physical stores and point-of-sale systems. Today’s retail enterprises operate complex, always-on digital ecosystems that span e-commerce platforms, mobile apps, omnichannel order management, supply chain systems, loyalty programs, personalization engines, and real-time analytics. Every product search, cart update, inventory check, price change, promotion, and payment depends on high-performing databases working … Continue reading “Running Retail on Data: How Enteros Transforms Database Performance Management”
Scaling Digital Banking with Confidence: AI SQL and Performance Intelligence by Enteros
- 5 February 2026
- Database Performance Management
Introduction Digital banking has moved from being a competitive differentiator to a baseline expectation. Customers now demand real-time payments, instant account access, personalized financial insights, always-on mobile experiences, and seamless digital onboarding—without delays, downtime, or friction. Behind these experiences lies an increasingly complex technology foundation. Core banking modernization, cloud-native digital platforms, open banking APIs, AI-powered … Continue reading “Scaling Digital Banking with Confidence: AI SQL and Performance Intelligence by Enteros”
Turning Database Performance into Revenue Intelligence: Enteros for US Financial Enterprises
Introduction In the US financial services market, technology performance is no longer just an IT concern—it is a direct driver of revenue, customer trust, and competitive advantage. Banks, fintechs, capital markets firms, insurers, and payments providers all operate in an environment defined by real-time transactions, digital-first customer expectations, regulatory scrutiny, and relentless pressure to improve … Continue reading “Turning Database Performance into Revenue Intelligence: Enteros for US Financial Enterprises”