Preamble
Oracle BETWEEN condition (also called BETWEEN operator) is used to obtain values within a range in SELECT, INSERT, UPDATE or DELETE sentences.
Syntax of BETWEEN condition in Oracle/PLSQL
expression BETWEEN value1 AND value2;
Parameters and arguments of the condition
- expression – Column or calculation.
- value1 and value2 – Two values that create an inclusion range with which the expression is compared.
Note:
The Oracle BETWEEN condition will return records where the expression is within the range from value1 to value2 (inclusive).
Example with numbers
Consider a couple of examples of Oracle BETWEEN conditions using numerical values. The following example uses the BETWEEN condition to obtain values within a numerical range.
For example:
SELECT *
FROM customers
WHERE customer_id BETWEEN 4000 AND 4999;
This BETWEEN example will return all rows from the customer_id table where customer_id is between 4000 and 4999 (inclusive). This is equivalent to the next SELECT:
SELECT *
FROM customers
WHERE customer_id >= 4000
AND customer_id <= 4999;
Example with dates
Next, let’s look at an example of how you will use Oracle BETWEEN with dates. In the following example, the BETWEEN condition is used to obtain values within the date range.
For example:
SELECT *
FROM order_details
WHERE order_date BETWEEN TO_DATE ('01.10.2016', 'dd.mm.yyyy')
AND TO_DATE ('31.10.2016', 'dd.mm.yyyy');
This BETWEEN example will return all entries from the order_details table where order_date is in the date range of October 1, 2016 and October 31, 2016 (inclusive). This is equivalent to the following SELECT sentence:
SELECT *
FROM order_details
WHERE order_date >= TO_DATE('01.10.2016', 'dd.mm.yyyy')
AND order_date <= TO_DATE('31.10.2016', 'dd.mm.yyyy');
Example of using the NOT operator
Oracle condition BETWEEN can be combined with Oracle operator NOT. Below is an example of how a BETWEEN condition can be combined with the NOT operator.
For example:
SELECT *
FROM customers
WHERE customer_id NOT BETWEEN 3000 AND 3500;
This Oracle BETWEEN example will return all rows from the customer_id table where customer_id is not between 3000 and 3500 (inclusive). This is equivalent to the following SELECT sentence:
SELECT *
FROM customers
WHERE customer_id < 3000
OR customer_id > 3500;
Oracle SQL Tutorial; Date column in where condition
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 Manufacturers Improve Database Performance Across Smart Factory and ERP Systems?
- 16 September 2026
- Software Engineering
Database performance monitoring for manufacturing helps manufacturers identify slow SQL queries, resource bottlenecks, unusual workload changes, locking, database waits, and capacity risks across ERP, MES, IoT, supply-chain, and smart factory systems. With continuous observability and AI-assisted analysis, manufacturing IT teams can detect problems earlier, troubleshoot faster, and maintain responsive applications across increasingly connected production environments. … Continue reading “How Can Manufacturers Improve Database Performance Across Smart Factory and ERP Systems?”
How Can AI-Powered Database Monitoring Help Energy Companies Prevent Critical Performance Issues?
AI-powered database monitoring for energy helps energy and utility companies detect abnormal database behavior, identify performance bottlenecks, analyze SQL workloads, and uncover potential problems before they disrupt important applications. By combining database observability, historical baselines, anomaly detection, predictive analytics, and root cause analysis, energy IT teams can move from reactive troubleshooting toward proactive database performance … Continue reading “How Can AI-Powered Database Monitoring Help Energy Companies Prevent Critical Performance Issues?”
How Can AI-Powered Database Monitoring Help Retailers Prevent Performance Downtime?
- 15 September 2026
- AIDatabase Performance Management
AI-powered database monitoring for retail helps retailers prevent downtime by continuously analyzing queries, latency, waits, locks, resource utilization, and workload behavior. Instead of waiting for failures, AI can identify unusual patterns and emerging bottlenecks earlier. Enteros combines database observability, anomaly detection, SQL intelligence, root cause analysis, predictive analytics, and cost-aware monitoring to support more reliable … Continue reading “How Can AI-Powered Database Monitoring Help Retailers Prevent Performance Downtime?”
How Can Telecom Companies Optimize Databases to Handle Growing Customer and Network Data?
Telecom companies can optimize databases by combining continuous observability, SQL tuning, workload analysis, capacity planning, anomaly detection, and cloud cost control. Effective telecom database optimization helps teams process growing customer and network data without sacrificing speed or reliability. Enteros supports this approach with AI-powered analytics, database observability, root cause analysis, predictive insights, and Cloud FinOps … Continue reading “How Can Telecom Companies Optimize Databases to Handle Growing Customer and Network Data?”