Documentation

influxdb3 delete database

The influxdb3 delete database command deletes a database.

Usage

influxdb3 delete database [OPTIONS] <DATABASE_NAME>

Arguments

  • DATABASE_NAME: The name of the database to delete. Valid database names are alphanumeric and start with a letter or number. Dashes (-) and underscores (_) are allowed.

    Environment variable: INFLUXDB3_DATABASE_NAME

Options

OptionDescription
-H--hostHost URL of the running InfluxDB 3 Core server (default is http://127.0.0.1:8181)
--hard-deleteWhen to hard delete data (never/now/default/timestamp). Default behavior is a soft delete that allows recovery
--tokenAuthentication token
--tls-caPath to a custom TLS certificate authority (for testing or self-signed certificates)
-h--helpPrint help information
--help-allPrint detailed help information

Option environment variables

You can use the following environment variables to set command options:

Environment VariableOption
INFLUXDB3_HOST_URL--host
INFLUXDB3_AUTH_TOKEN--token

Examples

In the examples below, replace the following:

  • DATABASE_NAME: Database name
  • AUTH_TOKEN: Authentication token

Delete a database

influxdb3 delete database 
DATABASE_NAME

Delete a database while specifying the token inline

influxdb3 delete database --token 
AUTH_TOKEN
DATABASE_NAME

Hard delete a database immediately

Permanently delete a database and all its data immediately without the ability to recover.

influxdb3 delete database --hard-delete now 
DATABASE_NAME

Hard delete a database at a specific time

Schedule a database for permanent deletion at a specific timestamp.

influxdb3 delete database --hard-delete "2024-01-01T00:00:00Z" 
DATABASE_NAME

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.6

Key enhancements in InfluxDB 3.6 and the InfluxDB 3 Explorer 1.4.

See the Blog Post

InfluxDB 3.6 is now available for both Core and Enterprise. This release introduces the 1.4 update to InfluxDB 3 Explorer, featuring the beta launch of Ask AI, along with new capabilities for simple startup and expanded functionality in the Processing Engine.

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