Documentation

Perform a basic SQL query

The InfluxDB SQL implementation is powered by the Apache Arrow DataFusion query engine which provides an SQL syntax similar to other relational query languages.

A basic SQL query that queries data from InfluxDB most commonly includes the following clauses:

* Required
  • * SELECT: Specify fields, tags, and calculations to output from a measurement or use the wildcard alias (*) to select all fields and tags from a measurement.
  • * FROM: Specify the measurement to query data from.
  • WHERE: Only return data that meets the specified conditions–for example, falls within a time range, contains specific tag values, or contains a field value outside a specified range.
SELECT
  temp,
  hum,
  room
FROM home
WHERE
  time >= '2024-12-19T08:00:00Z'
  AND time <= '2024-12-19T20:00:00Z'
  • Copy
  • Fill window

Result set

If at least one row satisfies the query, InfluxDB Clustered returns row data in the query result set. An SQL query result set includes columns listed in the query’s SELECT statement.

Basic query examples

Sample data

The following examples use the sample data written in the Get started writing data guide. To run the example queries and return results, write the sample data to your InfluxDB Clustered database before running the example queries.

Query data within time boundaries

  • Use the SELECT clause to specify what tags and fields to return. To return all tags and fields, use the wildcard alias (*).
  • Specify the measurement to query in the FROM clause.
  • Specify time boundaries in the WHERE clause. Include time-based predicates that compare the value of the time column to a timestamp. Use the AND logical operator to chain multiple predicates together.
SELECT *
FROM home
WHERE
  time >= '2024-12-19T08:00:00Z'
  AND time <= '2024-12-19T12:00:00Z'
  • Copy
  • Fill window

Query time boundaries can be relative or absolute.

Query with relative time boundaries

Query with absolute time boundaries

Query data using a time zone offset

Query data without time boundaries

To query data without time boundaries, do not include any time-based predicates in your WHERE clause.

Querying data without time bounds can return an unexpected amount of data. The query may take a long time to complete and results may be truncated.

SELECT * FROM home
  • Copy
  • Fill window

Query specific fields and tags

To query specific fields, include them in the SELECT clause. If querying multiple fields or tags, comma-delimit each. If a field or tag key includes special characters or spaces or is case-sensitive, wrap the key in double-quotes.

SELECT time, room, temp, hum FROM home
  • Copy
  • Fill window

Query fields based on tag values

  • Include the fields you want to query and the tags you want to base conditions on in the SELECT clause.
  • Include predicates in the WHERE clause that compare the tag identifier to a string literal. Use logical operators to chain multiple predicates together and apply multiple conditions.
SELECT * FROM home WHERE room = 'Kitchen'
  • Copy
  • Fill window

Query points based on field values

  • In the SELECT clause, include fields you want to query.
  • In the WHERE clause, include predicates that compare the field identifier to a value or expression. Use logical operators (AND, OR) to chain multiple predicates together and apply multiple conditions.
SELECT co, time FROM home WHERE co >= 10 OR co <= -10
  • Copy
  • Fill window

Alias queried fields and tags

To alias or rename fields and tags that you query, pass a string literal after the field or tag identifier in the SELECT clause. You can use the AS clause to define the alias, but it isn’t necessary. The following queries are functionally the same:

SELECT temp 'temperature', hum 'humidity' FROM home

SELECT temp AS 'temperature', hum AS 'humidity' FROM home
  • Copy
  • Fill window

Was this page helpful?

Thank you for your feedback!


The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Read more

InfluxDB v3 enhancements and InfluxDB Clustered is now generally available

New capabilities, including faster query performance and management tooling advance the InfluxDB v3 product line. InfluxDB Clustered is now generally available.

InfluxDB v3 performance and features

The InfluxDB v3 product line has seen significant enhancements in query performance and has made new management tooling available. These enhancements include an operational dashboard to monitor the health of your InfluxDB cluster, single sign-on (SSO) support in InfluxDB Cloud Dedicated, and new management APIs for tokens and databases.

Learn about the new v3 enhancements


InfluxDB Clustered general availability

InfluxDB Clustered is now generally available and gives you the power of InfluxDB v3 in your self-managed stack.

Talk to us about InfluxDB Clustered