# Saved queries overview

> [!WARNING]
>
> **Preview**
>
>
> This feature is
>
> subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the
> [Service Specific
> Terms](https://docs.cloud.google.com/terms/service-terms#1).
>
> Pre-GA features are available "as is" and might have limited support.
>
> For more information, see the
> [launch stage descriptions](https://cloud.google.com/products/#product-launch-stages).

To store, reuse, and share frequently run database statements without rewriting
them for each session, you can use saved queries 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 console; you
cannot run or manage saved queries through an API or other means.

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](https://docs.cloud.google.com/bigtable/docs/create-manage-saved-queries) in the Google Cloud console.
- You must have the correct [Identity and Access Management (IAM) role or permissions](https://docs.cloud.google.com/bigtable/docs/create-manage-saved-queries#required-roles) to view and manage saved queries.
- You can only access saved queries using 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:

- There is a rate limit of 20 queries per second (QPS) per user per project, including both read and write. This quota is not trackable or overridable.
- 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](https://docs.cloud.google.com/bigtable/quotas).
- You can't encrypt saved queries with [customer-managed encryption keys (CMEK)](https://docs.cloud.google.com/bigtable/docs/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

- Learn how to [create and manage saved queries](https://docs.cloud.google.com/bigtable/docs/create-manage-saved-queries).
- Learn how to [manage your data using Bigtable Studio](https://docs.cloud.google.com/bigtable/docs/manage-data-using-console).