Documentation

Delete a database

Use the influxdb3 delete database command, the HTTP API, or InfluxDB 3 Explorer to delete a database from InfluxDB 3 Enterprise.

Deleting a database cannot be undone

Deleting a database is a destructive action. Once a database is deleted, data stored in that database cannot be recovered.

Delete a database using the influxdb3 CLI

Provide the following:

  • Name of the database to delete
influxdb3 delete database 
DATABASE_NAME

Replace the following:

  • DATABASE_NAME: the name of the database to delete

Enter yes to confirm that you want to delete the database.

Delete a database using the HTTP API

To delete a database using the HTTP API, send a DELETE request to the /api/v3/configure/database endpoint:

DELETE localhost:8181/api/v3/configure/database

Include the following in your request:

  • Query parameters:
    • db: Database name to delete
  • Headers:
curl --request DELETE "localhost:8181/api/v3/configure/database?db=
DATABASE_NAME
"
\
--header "Authorization: Bearer
AUTH_TOKEN
"

Replace the following:

  • DATABASE_NAME: the name of the database to delete
  • AUTH_TOKEN: your admin token

Response

A successful deletion returns HTTP status 200 with no content body.

Delete a database using InfluxDB 3 Explorer

You can also delete databases using the InfluxDB 3 Explorer web interface:

  1. If you haven’t already, see how to get started with Explorer and connect to your InfluxDB 3 Enterprise server.
  2. In Explorer, click Databases in the left navigation.
  3. Find the database you want to delete in the list.
  4. Click the Delete icon (trash can) next to the database name.
  5. In the confirmation dialog, type the database name to confirm.
  6. Click Delete Database.

This action cannot be undone. All data in the database will be permanently deleted.

For more information, see Manage databases with InfluxDB 3 Explorer.

Delete data only (preserve schema and resources)

InfluxDB 3 Enterprise supports deleting only the data in a database while preserving the database schema and associated resources. This is useful when you want to clear old data and re-write new data to the same structure without recreating resources.

What is preserved

When using the data-only deletion option, the following are preserved:

  • Database schema: Tables and column definitions
  • Authentication tokens: Database-scoped access tokens
  • Processing engine configurations: Triggers and plugin configurations
  • Caches: Last value caches (LVC) and distinct value caches (DVC)

Delete data only using the CLI

Use the --data-only flag to delete data while preserving the database schema and resources–for example:

influxdb3 delete database --data-only 
DATABASE_NAME

Replace DATABASE_NAME with the name of your database.

Delete data and remove tables

To delete data and remove table schemas while preserving database-level resources (tokens, triggers, configurations), combine --data-only with --remove-tables:

influxdb3 delete database --data-only --remove-tables 
DATABASE_NAME

This preserves:

  • Authentication tokens
  • Processing engine triggers and configurations

But removes:

  • All data
  • Table schemas
  • Table-level caches (LVC and DVC)

Delete data only using the HTTP API

To delete only data using the HTTP API, include the data_only=true query parameter:

curl --request DELETE "localhost:8181/api/v3/configure/database?db=
DATABASE_NAME
&data_only=true"
\
--header "Authorization: Bearer
AUTH_TOKEN
"

Replace the following:

  • DATABASE_NAME: the name of the database
  • AUTH_TOKEN: your admin token

Delete data and remove tables

To also remove table schemas, add the remove_tables=true parameter:

curl --request DELETE "localhost:8181/api/v3/configure/database?db=
DATABASE_NAME
&data_only=true&remove_tables=true"
\
--header "Authorization: Bearer
AUTH_TOKEN
"

Was this page helpful?

Thank you for your feedback!


InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.8

Explorer 1.8 is now available with streaming data subscriptions (beta), line protocol preview, and query history & saved queries.

View Explorer 1.8 release notes

Explorer 1.8 includes new features and improvements that make it easier to ingest, explore, and manage data.

Highlights:

  • Streaming data subscriptions (beta): Stream data into Explorer from MQTT, Kafka, and AMQP sources.
  • Line protocol preview: Preview line protocol, schema, and parse errors before data is written.
  • Custom sample data: Generate custom sample datasets with line protocol and schema preview.
  • Query history and saved queries: Browse query history and save/re-run named queries.
  • Retention period management: Set, update, or clear retention periods on databases and tables.

For more details, see Explorer 1.8 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

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.7-beta now available

Telegraf Controller v0.0.7-beta is now available with new features, improvements, bug fixes, and an important breaking change.

View the release notes
Download Telegraf Controller v0.0.7-beta

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 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