Introduction to saved queries

This document provides an introduction to saved queries and classic saved queries in BigQuery.

Saved queries

Preview

This product or feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the Service Specific Terms. Pre-GA products and features are available "as is" and might have limited support. For more information, see the launch stage descriptions.

For support during the preview, email [e-mail].

This document provides an introduction to saved queries in BigQuery. You can use saved queries to create and manage SQL scripts. Saved queries improve collaboration and query management with the following options:

• Share queries with specific users and groups by using Identity and Access Management (IAM).
• Review the query version history.
• Revert to or branch from previous versions of the query.

Saved queries save both the query text and the query settings.

Saved queries are BigQuery Studio code assets powered by Dataform. Notebooks are also code assets. All code assets are stored in a default region. Updating the default region changes the region for all code assets created after that point.

Saved query capabilities are available only in the Google Cloud console.

Saved query security

You control access to saved queries by using Identity and Access Management (IAM) roles. For more information, see Grant access to saved queries.

Supported regions

The following tables list the regions where saved queries are available.

Americas

Region description	Region name	Details
Iowa	us-central1	Low CO2
Oregon	us-west1	Low CO2
São Paulo	southamerica-east1	Low CO2

Asia Pacific

Region description	Region name	Details
Mumbai	asia-south1
Singapore	asia-southeast1
Taiwan	asia-east1
Tokyo	asia-northeast1

Europe

Region description	Region name	Details
Belgium	europe-west1	Low CO2
Frankfurt	europe-west3	Low CO2
London	europe-west2	Low CO2
Netherlands	europe-west4
Zürich	europe-west6	Low CO2

Quotas and limits

For more information, see Saved query quotas and limits.

Classic saved queries

Classic saved queries are an earlier way of saving and sharing SQL queries. Classic saved queries provide the query text, and the only query setting retained by a classic saved query is the SQL version. This setting governs whether the query uses legacy SQL or GoogleSQL. To query the data, users must have access to the data that the saved query accesses. For more information, see Grant access to saved queries.

Note: If you are not enrolled in the BigQuery Studio preview, classic saved queries appear in the Saved queries (NUMBER) folder of the Explorer pane instead of the (Classic) Queries folder.

There are 3 types of classic saved queries:

• Private. Private classic saved queries are visible only to the user who creates them. They are identified with the icon.
• Project-level. Project-level saved queries are visible to principals that have the required permissions. They are identified with the icon.
• Public. Public classic saved queries are visible to anyone with a link to the query. They are identified with the icon.

You can migrate classic saved queries to saved queries to take advantage of the new capabilities, or continue to maintain them as classic saved queries.

The classic saved query feature is available only in the Google Cloud console.

What's next

• Learn how to create saved queries.
• Learn how to manage saved queries.