Is Sql Between Inclusive

SQL Programming

When working with SQL queries, the BETWEEN operator is a useful tool for filtering data within a specific range. This operator allows me to specify a range to filter results based on the values in a particular column. But I often wonder, is the range inclusive when using the BETWEEN operator?

Well, after diving into the technical details and putting it to the test in my own projects, I’ve come to a clear conclusion. The BETWEEN operator is indeed inclusive, meaning it includes the values specified in the range. This means that when I use BETWEEN 10 AND 20, it will include both 10 and 20 in the results.

Understanding the Syntax

The syntax of the BETWEEN operator is straightforward. When I use it in a SQL query, the syntax typically looks like this: column_name BETWEEN value1 AND value2. With this syntax, I can filter the data in the specified column to include values that fall within the range of value1 and value2, inclusive of the boundary values.

Practical Example

Let’s say I have a table of products with a column for their prices. If I want to retrieve products that are priced between $50 and $100, I can use the BETWEEN operator in my SQL query like this:

SELECT * FROM products WHERE price BETWEEN 50 AND 100;

When I execute this query, the result will include products that are priced at $50 and $100, as the BETWEEN operator is inclusive.

Be Mindful of Data Types

It’s essential to be mindful of the data types when using the BETWEEN operator. When working with date and time values, I need to ensure that the range is inclusive of the specified dates or times. In some cases, I may also need to consider the time component when using the BETWEEN operator with timestamp data.


After exploring the behavior of the BETWEEN operator in SQL and testing it in various scenarios, I can confidently affirm that it is indeed inclusive. This knowledge has proven to be valuable in my database querying endeavors, allowing me to precisely filter data within specific ranges. So, the next time I use BETWEEN in my SQL queries, I can do so with the assurance that it covers the specified range inclusively.