Sign inTry Free

Important

Self-managed SingleStore will soon transition from version 9.1 RC to version 10. This new semantic versioning scheme will provide SingleStore with finer control over engine and feature releases that were not possible with the current versioning scheme.

In the interim, SingleStore 9.1 RC can be used to preview, evaluate, and provide feedback on the new and upcoming features in SingleStore 10 prior to its general availability. Ahead of this transition, SingleStore 9.0 is recommended for production workloads, which can later be upgraded to SingleStore 10.

DROP DATABASE

On this page

The DROP DATABASE command drops a database.

Note

This command does not drop remote storage databases. To do that, use DETACH DATABASE.

Syntax

DROP DATABASE [IF EXISTS] <database_name> [FORCE]


DROP SCHEMA [IF EXISTS] <database_name> [FORCE]

Arguments

Remarks

  • By default, the DROP DATABASE command waits for the running queries to finish before dropping the database. To override this behavior and kill any running queries, use the FORCE option.

  • The DROP DATABASE command can be run on the master aggregator node, or a child aggregator node when DDL Forwarding is enabled. See Node Requirements for SingleStore Commands).

  • This command causes implicit commits. Refer to COMMIT for more information.

  • The DROP DATABASE command cannot be run on system databases.

  • The DROP DATABASE command drops the Point-In-Time Recovery (PITR) history. A database cannot be restored to the PITR milestone taken before the database was dropped.

  • Refer to the Permissions Matrix for the required permissions.

Examples

DROP DATABASE IF EXISTS test;
DROP DATABASE IF EXISTS db FORCE;

Last modified:

Was this article helpful?

On this page

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In