Create saved queries

When you write SQL in the query editor, you can save your query and share your query with others. Saved queries are BigQuery Studio code assets powered by Dataform.

For more information on deleting saved queries and managing saved query history, see Manage saved queries.

Required permissions

Set the appropriate permissions to create, edit, or view saved queries.

All users with the Dataform Admin (roles/dataform.admin) role have owner access to all saved queries created in the project.

For more information about BigQuery Identity and Access Management (IAM), see Access control with IAM.

Permissions to create saved queries

To create and run saved queries, you need the following IAM permissions:

• dataform.locations.get
• dataform.locations.list
• dataform.repositories.list

• dataform.repositories.create

  Note: Users who have the dataform.repositories.create permission can execute code using the default Dataform service account and all permissions granted to that service account. For more information, see Security considerations for Dataform permissions.

You can get these permissions from the following IAM roles:

• BigQuery Job User (roles/bigquery.jobUser)
• BigQuery Read Session User (roles/bigquery.readSessionUser)

• Code Creator (roles/dataform.codeCreator)

  Note: Users assigned the Code Creator role in a project can list the names of code assets in that project by using the Dataform API or the Dataform command-line interface (CLI). Non-administrators using BigQuery Studio can only see code assets that they created or that were shared with them.

Permissions to edit saved queries

To edit and run saved queries, you need the following IAM roles:

• BigQuery Job User (roles/bigquery.jobUser)
• BigQuery Read Session User (roles/bigquery.readSessionUser)
• Code Editor (roles/dataform.codeEditor)

Permissions to view saved queries

To view and run saved queries, you need the following IAM roles:

• BigQuery Job User (roles/bigquery.jobUser)
• BigQuery Read Session User (roles/bigquery.readSessionUser)
• Code Viewer (roles/dataform.codeViewer)

Set the default region for code assets

If this is the first time you are creating a code asset, you should set the default region for code assets. You can't change the region for a code asset after it is created.

Note: If you create a saved query and choose a different default region than the one you have been using for code assets, for example choosing us-west1 when you have been using us-central1, then that query and all code assets you create afterwards use that new region by default. Existing code assets continue to use the region they were assigned when they were created.

All code assets in BigQuery Studio use the same default region. To set the default region for code assets, follow these steps:

1. Go to the BigQuery page.

   Go to BigQuery

2. In the Explorer pane, find the project in which you have enabled code assets.

3. Click View actions next to the project, and then click Change my default code region.

4. For Region, select the region that you want to use for code assets.

5. Click Select.

For a list of regions where is available, see BigQuery Studio locations.

Create saved queries

To create a saved query, follow these steps:

1. In the Google Cloud console, go to the BigQuery page.

   Go to BigQuery

2. Click SQL query.

3. In the query editor, enter a valid SQL query. For example, you can query a public dataset:

   SELECT
     name,
     SUM(number) AS total
   FROM
     `bigquery-public-data.usa_names.usa_1910_2013`
   GROUP BY
     name
   ORDER BY
     total DESC
   LIMIT
     10;

4. Click Save > Save query or press Control+S.

5. In the Save query dialog, type a name for the saved query.

6. Optional: To change the region used by this saved query and all other code assets in the future, select a new region in Region.

7. Click Save.

   The first version of the saved query is created.

Share saved queries

To share a saved query with a user, you first grant that user access to the saved query and add them to an appropriate IAM role. Then you generate a link to the saved query and share that link with the user.

Users that you share a query with only see the most recent version of a query. Autosaved changes that you haven't explicitly saved don't appear in the shared query.

1. In the Google Cloud console, go to the BigQuery page.

   Go to BigQuery

2. In the Explorer pane, expand your project and the Queries folder, and if necessary, the Shared queries folder. Find and click the saved query that you want to grant access to.

3. Click Share, and then click Manage permissions.

4. In the Manage permissions pane, click Add user/group.

5. In the New principals field, enter a principal.

6. In the Role list, select one of the following roles:

   • Code Owner: can perform any action on the saved query, including deleting or sharing it.
   • Code Editor: can edit the query.
   • Code Viewer: can view the query.
   Note: The principal must also have the BigQuery User (roles/bigquery.user) role to run the saved query.

7. Optional: To view a complete list of roles and advanced sharing settings, click Advanced sharing.

8. Click Save.

9. To return to the saved query info, click Close.

10. To generate a link to the saved query, click Share, and then click Get link.

    The link is copied to your clipboard.

Open a saved query version as a new query

To open any version of an existing saved query as a new query, follow these steps:

1. In the Google Cloud console, go to the BigQuery page.

   Go to BigQuery

2. In the Explorer pane, expand your project and the Queries folder, and if necessary, the Shared queries folder. Select a saved query.

3. Click Version history.

4. Click View actions next to a saved query version and then click Open as new query.

Update saved queries

Changes that you make to the text of a saved query are automatically saved two seconds after you stop typing and appear in your Version history as Your changes. Autosaved changes aren't a new version of the query. Your autosaved changes reappear any time you open the query but aren't visible to anyone else unless you explicitly save them as a new version of the query. Autosaved queries are in Preview.

1. In the Google Cloud console, go to the BigQuery page.

   Go to BigQuery

2. In the Explorer pane, expand your project and the Queries folder, and if necessary, the Shared queries folder. Click the name of a saved query to open it.

3. Modify the query.

4. To save the modified query, click Save query > Save query or press Control+S (or Command+S on macOS).

   A new version of the query is created.

Upload saved queries

You can upload a local SQL query to use it as a saved query in BigQuery Studio. The uploaded saved query is then also visible in the BigQuery page of the Google Cloud console.

To upload a saved query, follow these steps:

1. In the Google Cloud console, go to the BigQuery page.

   Go to BigQuery

2. In the Explorer pane, expand your project, and then do one of the following:

   • Next to Queries, click View actions > Upload SQL query.
   • Next to the Google Cloud project name, click View actions > Upload to project > SQL query.

3. In the Upload SQL dialog, in the SQL field, click Browse, and then select the query that you want to upload.

4. Optional: In the SQL name field, edit the name of the query.

5. In the Region field, select the region where you want to upload your saved query.

6. Click Upload.

Your saved query appears in the Explorer pane.

Classic saved queries

Deprecated: Saved queries, available in BigQuery Studio, will fully replace classic saved queries in the future. The deprecation timeline is being reviewed. For more information, see Deprecation of classic saved queries. To learn how to migrate to saved queries, see Migrate classic saved queries.

Use the following sections to learn how to create and update classic saved queries. For more information on sharing, migrating, and deleting classic saved queries, see Classic saved queries.

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

Required permissions for classic saved queries

The following IAM permissions are required to create, view, update, and delete classic saved queries:

• Private classic saved queries:
  • Creating private classic saved queries requires no special permissions. You can save a private query in any project, but only you can view, update, or delete the query.
• Project-level classic saved queries:
  • Creating a project-level classic saved query requires bigquery.savedqueries.create permissions. The bigquery.admin predefined role includes bigquery.savedqueries.create permissions.
  • Viewing a project-level classic saved query requires bigquery.savedqueries.get and bigquery.savedqueries.list permissions. The bigquery.admin and bigquery.user predefined roles include bigquery.savedqueries.get and bigquery.savedqueries.list permissions.
  • Updating a project-level classic saved query requires bigquery.savedqueries.update permissions. The bigquery.admin predefined role includes bigquery.savedqueries.update permissions.
  • Deleting a project-level classic saved query requires bigquery.savedqueries.delete permissions. The bigquery.admin predefined role includes bigquery.savedqueries.delete permissions.
• Public classic saved queries:
  • Creating public classic saved queries requires no special permissions. You can save a public classic saved query in any project, but only you can update or delete the query. Anyone with the link can view a public classic saved query.

Note: Users given the dataform.repository.list permission at the project level can see all saved queries created in the project.

For more information on IAM roles in BigQuery, see Predefined roles and permissions.

Create classic saved queries

1. In the Google Cloud console, go to the BigQuery page.

   Go to BigQuery

2. Click SQL query.

3. In the query editor, enter a valid SQL query. For example, you can query a public dataset:

   SELECT
     name,
     SUM(number) AS total
   FROM
     `bigquery-public-data.usa_names.usa_1910_2013`
   GROUP BY
     name
   ORDER BY
     total DESC
   LIMIT
     10;

4. Click Save Query (Classic) > Save query (Classic).

5. In the Save query dialog, enter a name for your query, and then set Visibility to one of the following options:

   • Personal (editable only by you) for a private clasic shared query.
   • Project (editable by principals with appropriate permissions) for a project-level classic saved query.
   • Public for a public classic saved query.

6. Click Save.

Share classic saved queries

You can share classic saved queries that you have given project or public visibility. Project visibility allows principals with the required permissions to view, update, or delete the query. Public visibility allows anyone with the query link to view but not update or delete the query.

You share a classic saved query with other users by generating and sharing a link to the classic saved query.

To run a classic shared query, users must have access to the data that the query accesses. For more information, see Grant access to a dataset.

If you are plan to share a classic saved query, consider including a comment in the query that describes its purpose.

1. In the Explorer pane, expand your project and the (Classic) Queries folder, and then find the classic saved query you want to share.
2. Click View actions next to the query and then click Get link.
3. Share the link with the users you want to grant access to the query.

Update classic saved queries

1. In the Google Cloud console, go to the BigQuery page.

   Go to BigQuery

2. In the Explorer pane, expand your project and the (Classic) Queries folder, and if necessary, the Project queries folder.

3. Click the name of a classic saved query to open it.

4. Modify the query.

5. To save the modified query, click Save Query (Classic) > Save query (Classic).

What's next

• Learn how to manage saved queries.