Documentation

Rename a database

Use the influxctl database rename command to rename a database in your InfluxDBed cluster.

Renaming a database does not change the database ID, modify data in the database, or update database tokens. After renaming a database, any existing database tokens will stop working and you must create new tokens with permissions for the renamed database.

If you create a new database using the previous database name, tokens associated with that database name will grant access to the newly created database.

Rename a database using the influxctl CLI

influxctl database rename 
DATABASE_NAME
NEW_DATABASE_NAME

Replace the following:

  • DATABASE_NAME: Current name of the database to rename
  • NEW_DATABASE_NAME: New name for the database

Update database tokens after renaming

After renaming a database, existing database tokens will no longer work because they reference the old database name. Do the following:

  1. Create new database tokens with permissions for the renamed database.
  2. Update your applications and clients to use the new tokens.
  3. Delete the old database tokens that reference the old database name.

Renamed database retains its ID

The database ID remains the same after renaming. When you list databases, you’ll see the new name associated with the original database ID.


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value cachesβ€”making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, 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