Documentation

influxctl database delete

The influxctl database delete command deletes a database from an InfluxDB cluster.

Usage

influxctl database delete [command options] [--force] <DATABASE_NAME> [<DATABASE_NAME_N>...]

Cannot be undone

Deleting a database is a destructive action that cannot be undone.

Wait before writing to a new database with the same name

After deleting a database from your InfluxDB cluster, you can reuse the name to create a new database, but wait two to three minutes after deleting the previous database before writing to the new database to allow write caches to clear.

Tokens still grant access to databases with the same name

Database tokens are associated to databases by name. If you create a new database with the same name, tokens that granted access to the deleted database will also grant access to the new database.

Arguments

ArgumentDescription
DATABASE_NAMEName of the database to delete

Flags

FlagDescription
--forceDo not prompt for confirmation to delete (default is false)
-h--helpOutput command help

Examples

Delete a database named “mydb”
influxctl database delete mydb
Delete multiple databases
influxctl database delete mydb1 mydb2

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