Preamble
The Oracle/PLSQL MIN function returns the minimum value of the expression.
Oracle/PLSQL syntax of MIN function
SELECT MIN(aggregate_expression_id)
FROM tabs
[WHERE conds]
OR syntax for MIN function with results grouped in one or more columns:
SELECT expression1_id, expression2_id, ... expression_n_id,
MIN(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 MIN function must be included in the GROUP BY operator at the end of the SQL sentence.
- aggregate_expression_id – is a column or expression from which the minimum value will be returned.
- tabs – tables from which you want to get records. At least one table must be specified in FROM operator.
- WHERE conds – optional. These are the conditions that must be met for the selected records.
MIN function in the following versions of Oracle/PLSQL
Oracle 12c, Oracle 11g, Oracle 10g, Oracle 9i, Oracle 8i
|
One Field Example
Let’s consider examples of the MIN function and learn how to use the MIN function in Oracle/PLSQL.
For example, you will want to know what is the minimum wage for all employees.
SELECT MIN(salary_id) AS "Lowest Salary"
FROM empls;
The query above will return the minimum wage for all employees from the employees table.
Example – Using GROUP BY
In some cases, you may need to use GROUP BY with MIN function.
For example, you might also want to use the MIN function to return the department and MIN(salary) to the department.
SELECT depart, MIN(salary_id) AS "Lowest salary".
FROM empls
GROUP BY depart;
Since your SELECT operator has one column that is not encapsulated in the MIN 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
Unlocking RevOps Efficiency in the Banking World with AIOps-Powered Database Technology and Root Cause Analysis—Driven by Enteros
- 15 September 2025
- Database Performance Management
Introduction The banking sector has long been a pioneer in adopting cutting-edge technologies to maintain security, efficiency, and customer trust. From mobile banking apps and real-time payments to fraud detection systems and risk management models, financial institutions operate on massive volumes of data and complex database infrastructures. But with this dependency comes a unique set … Continue reading “Unlocking RevOps Efficiency in the Banking World with AIOps-Powered Database Technology and Root Cause Analysis—Driven by Enteros”
Driving Technology Sector Growth with Enteros: AI-Powered Database Performance, Cloud FinOps, and Next-Gen Database Software
Introduction The technology sector is at the heart of global digital transformation. From software-as-a-service (SaaS) providers to enterprise IT vendors, cloud-native startups, and global hyperscalers, the industry is both the builder and consumer of massive-scale digital infrastructure. To remain competitive, technology companies must ensure optimal database performance, leverage the power of artificial intelligence (AI), adopt … Continue reading “Driving Technology Sector Growth with Enteros: AI-Powered Database Performance, Cloud FinOps, and Next-Gen Database Software”
NFT drops failing: how DB lags ruin million-dollar launches
When Seconds Decide Millions Imagine this: a highly anticipated NFT collection drops at midnight. Thousands of wallets flood in, bidding wars begin, prices spike. And then—suddenly—the marketplace freezes. Transactions hang, bids vanish, collectors complain on Twitter, and the brand’s reputation tanks overnight. This isn’t a rare story in Web3. It’s a database story. In this … Continue reading “NFT drops failing: how DB lags ruin million-dollar launches”
911 call centers under DB overload: response delayed
Introduction In emergencies, every second is the difference between life and death. Yet as 911 call centers shift to fully digital systems, they face an invisible but growing threat: database performance. When the data layer lags, critical decisions—from dispatching ambulances to locating callers—can be delayed, putting lives at risk. How Databases Power Emergency Response Modern … Continue reading “911 call centers under DB overload: response delayed”