Documentation

influxctl database delete

The influxctl database delete command deletes a database from an InfluxDB Cloud Dedicated 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 Cloud Dedicated 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!


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