Delete a Database

Stable

How to safely delete a database in SPG99 and what to expect from asynchronous deletion.

Updated: March 5, 2026

Deleting a database in SPG99 is an asynchronous destructive operation. After the request, the database may still remain visible in the catalog for some time with the status deleting.

How to delete a database

Through the API:

DELETE /v2/tenants/:tenant/dbs/:db?force=true

Through the CLI:

spgctl db delete --tenant acme --db app --force

What happens after the request

The platform performs the necessary lifecycle steps on its own:

  • marks the database as deleting;
  • terminates active compute if necessary;
  • cleans up related storage entities;
  • removes the record from the catalog.

The user does not need to stop the database separately “just in case” before a normal deletion.

What to check before deletion

Before deleting, make sure that:

  • the application no longer uses this database;
  • the necessary data has already been saved or migrated;
  • the team understands that the operation is irreversible;
  • you are deleting the correct database in the correct tenant.

What to do after deletion

A normal check looks like this:

  1. read the database state again or get the tenant database list;
  2. wait until the object disappears or reaches its final state;
  3. remove outdated DSNs and secrets from applications and CI.

Practical advice

For production, it is better to verify first that all applications have already been switched over or stopped. Database deletion itself is asynchronous, so do not be alarmed if the object does not disappear immediately.