MV_CLOUD_ATTACHED_DATABASES

This view shows information about all the attached databases and branches.

This view is intended for internal SingleStore use. No additional information is available.

Note

This view is only applicable for SingleStore Helios.

Column Name	Description
DATABASE_NAME	The name of the attached database.
SITE_NAME	Name of the site on which the database is attached.
ATTACH_TYPE	`READONLY` or `READWRITE`.
STORAGE_ID	This is the unique identifier for the backend storage associated with the attached database/branch. It is the storage identity for the currently attached database entry shown in the same row. Use this value together with `COMPUTE_ID` when attaching/re-attaching databases to ensure there is no ambiguity.
COMPUTE_ID	This uniquely identifies the workspace compute attachment for that attached database row. `STORAGE_ID` and `COMPUTE_ID` represent different layers: storage vs compute attachment.
ATTACH_SYNTAX	Syntax to attach this database on a potential workspace.
ATTACH_MEMO	Optional memo string during attach. Note: Some internal functions such as `FAILOVER`/`FAILBACK` may automatically populate this field.

Last modified: June 9, 2026

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.

(Optional) Run the following command to view the associated signature files.
Shell
```
curl undefined
```
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.
  Shell
```
curl -O undefined
```

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

Shell

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