milestone_name

A quoted string that specifies the milestone from which to detach the database.

FORCE

The FORCE argument allows you to terminate ongoing uploads to remote storage and forcibly detach the database. This can be useful in situations where, for example, the detach process is unable to upload blobs to remote storage or encounters a connection loss error - scenarios in which the database cannot be detached normally and the process may become stuck.

The FORCE option is applicable only for clusters using unlimited storage and is intended primarily for emergency recovery. It is not recommended for routine use.

When the FORCE argument is not included, all outstanding changes are uploaded into remote storage before detaching.

When the FORCE argument is included, SingleStore immediately stops all ongoing uploads and detaches the database. Any data not yet uploaded to remote storage, such as columnstore blobs, rowstore data, or logs, will be lost, resulting in potential data loss. Note that this operation only detaches the database, and does not drop or delete it.

To reattach the database, use the ATTACH DATABASE command. While SingleStore restores the database, any data that was not previously uploaded to remote storage will be missing after reattachment.

KILL

The KILL argument is less disruptive than FORCE, but serves a similar purpose. If detaching a database fails due to a long-running query, you can use the KILL argument to terminate the active query or workload and then proceed with detaching the database.

Unlike FORCE, the KILL argument only stops currently running queries and ensures that all data is uploaded to remote storage before the database is detached. This means that when you later reattach the database, all your data previously uploaded to remote storage will be available. Only the data from the terminated query will be lost, as it was stopped before the detach operation completed.

Examples

DETACH DATABASE db AT MILESTONE "m";

DETACH DATABASE db KILL;