Saved queries overview

This page describes how saved queries work in Bigtable.

You can use Bigtable Studio to create, save, and manage SQL scripts as saved queries. The saved queries capability is available only in the Google Cloud console.

Saved queries have the following characteristics:

  • Google-owned and Google-managed encryption keys encrypt all queries at rest.
  • A saved query is a child of a project.
  • Saved queries are deleted when the project is deleted. If you delete the instance or database, you can still access saved queries in the project using the Saved queries page in the Google Cloud console.
  • You must have the correct Identity and Access Management (IAM) role or permissions to view and manage saved queries.
  • You can only access saved queries using the Bigtable Studio or by navigating to the Saved queries page in the Google Cloud console. Saved queries aren't accessible through the API.

Storage location

Bigtable attempts to store queries in the same location as the database. However, storage for saved queries is available in a limited number of locations, so it might select another region by default. To view and update the location where your saved queries are stored, first click Show Advanced Options from the save subtask. Then, from the Region list, select an available location.

Limitations

Saved queries has the following limitations:

  • You can't create more than 10,000 saved queries in a project—including saved queries for other Google Cloud products. For more information, see Quotas and limits.
  • You can't encrypt saved queries with customer-managed encryption keys (CMEK), even if the source Bigtable instance uses CMEK encryption.

Pricing

There is no additional charge for using or storing saved queries.

What's next