Documentation

Manage databases

An InfluxDB database is a named location where time series data is stored. Each InfluxDB database has a retention period.

If coming from InfluxDB v1, the concepts of databases and retention policies have been combined into a single concept–database. Retention policies are no longer part of the InfluxDB data model. However, InfluxDB Cloud Dedicated does support InfluxQL, which requires databases and retention policies. See InfluxQL DBRP naming convention.

If coming from InfluxDB v2, InfluxDB Cloud (TSM), or InfluxDB Cloud Serverless, database and bucket are synonymous.

Retention periods

A database retention period is the maximum age of data stored in the database. The age of data is determined by the timestamp associated with each point. When a point’s timestamp is beyond the retention period (relative to now), the point is marked for deletion and is removed from the database the next time the retention enforcement service runs.

The minimum retention period for and InfluxDB database is 1 hour. The maximum retention period is infinite meaning data does not expire and will never be removed by the retention enforcement service.

Table and column limits

You can customize table (measurement) limits and table column limits when you create or update a database in InfluxDB Cloud Dedicated.

Table limit

Default maximum number of tables: 500

Each measurement is represented by a table in a database. Your database’s table limit can be raised beyond the default limit of 500. InfluxData has production examples of clusters with 20,000+ active tables across multiple databases.

Increasing your table limit affects your InfluxDB Cloud Dedicated cluster in the following ways:

May improve query performance View more info

More PUTs into object storage View more info

More work for the compactor View more info

Column limit

Default maximum number of columns: 250

Configurable maximum number of columns: 1000

Each row must include a time column, with the remaining columns representing tags and fields. As a result, a table with 250 columns can have one time column and up to 249 field and tag columns.

If you attempt to write to a table and exceed the column limit, the write request fails and InfluxDB returns an error.

If you update the column limit for a database, the limit applies to newly created tables; doesn’t override the column limit for existing tables.

Increasing your column limit affects your InfluxDB Cloud Dedicated cluster in the following ways:

May adversely affect system performance


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