Documentation

influxdb3 update database

The influxdb3 update database command updates an existing database in your InfluxDB 3 Enterprise instance.

Use this command to update a database’s retention period.

Usage

influxdb3 update database [OPTIONS] --database <DATABASE_NAME>

Arguments

  • DATABASE_NAME: (Required) The name of the database to update.

You can also set the database name using the INFLUXDB3_DATABASE_NAME environment variable.

Options

OptionDescription
-H--hostHost URL of the running InfluxDB 3 Enterprise server (default is http://127.0.0.1:8181)
-d--databaseThe name of the database to update
--tokenAuthentication token
-r--retention-periodThe retention period as a duration value (for example: 30d, 24h) or none to clear
--tls-caPath to a custom TLS certificate authority (for testing or self-signed certificates)
--tls-no-verifyDisable TLS certificate verification (Not recommended in production, useful for self-signed certificates)
-h--helpPrint help information
--help-allPrint detailed help information

Option environment variables

You can use the following environment variables instead of providing CLI options directly:

Environment VariableOption
INFLUXDB3_HOST_URL--host
INFLUXDB3_DATABASE_NAME--database
INFLUXDB3_AUTH_TOKEN--token
INFLUXDB3_TLS_CA--tls-ca
INFLUXDB3_TLS_NO_VERIFY--tls-no-verify

Examples

The following examples show how to update a database.

In your commands replace the following:

  • DATABASE_NAME: Database name
  • AUTH_TOKEN: Authentication token

Update a database retention period

Updates a database retention period to 30 days.

influxdb3 update database --retention-period 30d --database 
DATABASE_NAME

Clear a database retention period

Removes the retention period from a database by setting it to none.

influxdb3 update database --retention-period none --database 
DATABASE_NAME

Update a database with authentication

Updates a database using an authentication token.

influxdb3 update database --token 
AUTH_TOKEN
--retention-period 7d --database
DATABASE_NAME

Was this page helpful?

Thank you for your feedback!


InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

Telegraf Controller v0.0.6-beta now available

Telegraf Controller v0.0.6-beta is now available with new features, improvements, and bug fixes.

View the release notes
Download Telegraf Controller v0.0.6-beta

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2