Documentation

Delete a table

Use the Admin UI or the influxctl table delete command to delete a table from a database in your InfluxDB Cloud Dedicated cluster.

Deleting a table is irreversible. Once a table is deleted, all data stored in that table is permanently removed and cannot be recovered.

Provide the following arguments:

  • Database name: Name of the database that contains the table to delete
  • Table name: Name of the table to delete
influxctl table delete 
DATABASE_NAME
TABLE_NAME

Replace the following:

  • DATABASE_NAME: Name of the database that contains the table to delete
  • TABLE_NAME: Name of the table to delete

When prompted, enter y to confirm the deletion.

Wait before reusing a deleted table name

After deleting a table, wait a few minutes before attempting to create a new table with the same name to ensure the deletion process has fully completed.

InfluxDB Cloud Dedicated creates tables implicitly using table names specified in line protocol written to the databases. To prevent the deleted table from being immediately recreated by incoming write requests, pause all write requests to the table before deleting it.


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