This page describes how saved queries work in Cloud SQL for MySQL
.
You can use Cloud SQL 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:
All queries are encrypted.
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 can only access saved queries using the Cloud SQL Studio or by navigating to the Saved queries page
in the Google Cloud console. Saved queries aren't accessible through the API.
Storage location
Cloud SQL for MySQL
stores all saved
queries in the us-central1 region.
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
.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-20 UTC."],[],[],null,["# Saved queries overview\n\n\u003cbr /\u003e\n\nMySQL \\| [PostgreSQL](/sql/docs/postgres/saved-queries \"View this page for the PostgreSQL database engine\") \\| [SQL Server](/sql/docs/sqlserver/saved-queries \"View this page for the SQL Server database engine\")\n\n\u003cbr /\u003e\n\n|\n| **Preview**\n|\n|\n| This feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nThis page describes how saved queries work in Cloud SQL for MySQL\n.\n\nYou can use Cloud SQL Studio\nto create, save, and manage SQL scripts as saved queries. The saved queries capability is\navailable only in the Google Cloud console.\n\nSaved queries have the following characteristics:\n\n- All queries are encrypted.\n- A saved query is a child of a project.\n- 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](/sql/docs/mysql/create-manage-saved-queries) in the Google Cloud console.\n- You must have the correct [Identity and Access Management (IAM) role or permissions](/sql/docs/mysql/create-manage-saved-queries#required-roles) to view and manage saved queries.\n- You can only access saved queries using the Cloud SQL Studio or by navigating to the **Saved queries** page in the Google Cloud console. Saved queries aren't accessible through the API.\n\nStorage location\n----------------\n\nCloud SQL for MySQL\nstores all saved\nqueries in the `us-central1` region.\n\nLimitations\n-----------\n\nSaved queries has the following limitations:\n\n- 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](/sql/docs/quotas) .\n- You can't use [customer-managed encryption keys](/spanner/docs/cmek) for instances with saved queries.\n\nPricing\n-------\n\nThere is no additional charge for using or storing saved queries.\n\nWhat's next\n-----------\n\n- Learn how to [create and manage saved queries](/sql/docs/mysql/create-manage-saved-queries) .\n- Learn how to [manage data using the Google Cloud console](/sql/docs/mysql/manage-data-using-studio) ."]]
