Documentation

Delete a database

Use the influxctl CLI or the Management HTTP API to create a database in your InfluxDB Cloud Dedicated cluster.

Deleting a database cannot be undone

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

Cannot reuse database names

After a database is deleted, you cannot reuse the same name for a new database.

  1. If you haven’t already, download and install the influxctl CLI, and then configure an influxctl connection profile for your cluster.

  2. In your terminal, run the influxctl database delete command and provide the following:

    • Name of the database to delete
  3. Confirm that you want to delete the database.

influxctl database delete 
DATABASE_NAME

This example uses cURL to send a Management HTTP API request, but you can use any HTTP client.

  1. If you haven’t already, follow the instructions to install cURL for your system.

  2. In your terminal, use cURL to send a request to the following InfluxDB Cloud Dedicated endpoint:

    DELETE https://console.influxdata.com/api/v0/accounts/ACCOUNT_ID/clusters/CLUSTER_ID/databases/DATABASE_NAME

    In the URL, provide the following:

    Provide the following request headers:

    Specify the DELETE request method.

The following example shows how to use the Management API to delete a database:

curl \
   --location "https://console.influxdata.com/api/v0/accounts/
ACCOUNT_ID
/clusters/
CLUSTER_ID
/databases/
DATABASE_NAME
"
\
--request DELETE \ --header "Accept: application/json" \ --header "Authorization: Bearer
MANAGEMENT_TOKEN
"

Replace the following in your request:

  • ACCOUNT_ID: the ID of the InfluxDB Cloud Dedicated account to create the database for
  • CLUSTER_ID: the ID of the InfluxDB Cloud Dedicated cluster to create the database for
  • MANAGEMENT TOKEN: a management token for your InfluxDB Cloud Dedicated cluster
  • DATABASE_NAME: your InfluxDB Cloud Dedicated database

Was this page helpful?

Thank you for your feedback!


The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: