Documentation

influxctl database rename

The influxctl database rename command renames a database in an InfluxDB Cloud Dedicated cluster. This command does not change the database ID, database properties, or the data stored in the database.

Renaming a database requires new tokens

Database tokens are associated to databases by name. After renaming a database, tokens referencing the old name no longer function. You must generate tokens for the new database name.

Usage

influxctl database rename [flags] <CURRENT_DB_NAME> <NEW_DB_NAME>

Arguments

ArgumentDescription
CURRENT_DB_NAMECurrent name of the database
NEW_DB_NAMENew name for the database

Flags

FlagDescription
-h--helpOutput command help

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.7

Key enhancements in InfluxDB 3.7 and the InfluxDB 3 Explorer 1.5.

See the Blog Post

InfluxDB 3.7 is now available for both Core and Enterprise, landing alongside version 1.5 of the InfluxDB 3 Explorer UI. This release focuses on giving developers faster visibility into what their system is doing with one-click monitoring, a streamlined installation pathway, and broader updates that simplify day-to-day operations.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 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