[[["์ดํดํ๊ธฐ ์ฌ์","easyToUnderstand","thumb-up"],["๋ฌธ์ ๊ฐ ํด๊ฒฐ๋จ","solvedMyProblem","thumb-up"],["๊ธฐํ","otherUp","thumb-up"]],[["์ดํดํ๊ธฐ ์ด๋ ค์","hardToUnderstand","thumb-down"],["์๋ชป๋ ์ ๋ณด ๋๋ ์ํ ์ฝ๋","incorrectInformationOrSampleCode","thumb-down"],["ํ์ํ ์ ๋ณด/์ํ์ด ์์","missingTheInformationSamplesINeed","thumb-down"],["๋ฒ์ญ ๋ฌธ์ ","translationIssue","thumb-down"],["๊ธฐํ","otherDown","thumb-down"]],["์ต์ข ์ ๋ฐ์ดํธ: 2025-08-18(UTC)"],[],[],null,["# Operational guidelines\n\n\u003cbr /\u003e\n\n[MySQL](/sql/docs/mysql/operational-guidelines \"View this page for the MySQL database engine\") \\| PostgreSQL \\| [SQL Server](/sql/docs/sqlserver/operational-guidelines \"View this page for the SQL Server database engine\")\n\n\u003cbr /\u003e\n\nThe Cloud SQL [Service Level Agreement (SLA)](/sql/sla) excludes outages \"caused by factors outside\nof Google's reasonable control\". This page describes some of the user-controlled\nconfigurations that can cause an outage for a Cloud SQL instance to be\nexcluded.\n\nIntroduction\n------------\n\nCloud SQL strives to give you as much control over how your instance is\nconfigured as possible. This includes some configurations that increase the risk\nof instance downtime, depending on the load and other configuration parameters.\nIf your instance becomes unhealthy, and Cloud SQL determines that it was out of\ncompliance with the operational limits as described on this page, then the\ndowntime period is not covered by (or does not count against) the\nCloud SQL [SLA](/sql/sla).\n\nThis list of operational limits is presented to inform you which configurations\npresent these risks, ways to avoid these\nconfigurations, and ways to mitigate the risks when the configuration is\nrequired for your business environment.\n| **Note:** You are responsible for monitoring your instance to ensure that it is properly sized and configured for the size and type of load it is experiencing.\n\nExcluded configurations\n-----------------------\n\nThe excluded configurations fall into the following categories:\n\n- General configuration requirements\n- Database flag values\n- Resource constraints\n\n### General configuration requirements\n\nOnly Cloud SQL instances configured for high availability with at least one\ndedicated CPU are covered by the Cloud SQL [SLA](/sql/sla). Shared-core instances and single-zone\ninstances are not covered by the SLA.\n\nIf the instance is configured and used in a way that causes the workload\nto overload the instance or the instance to experience a long recovery time,\nthen the SLA does not apply.\n\nWe strongly advise you to set up alerts and monitoring\nin [Cloud Monitoring](/sql/docs/mysql/monitor-instance).\n\n### Database flag values\n\nCloud SQL lets you configure your instance using [database\nflags](/sql/docs/postgres/flags). Some of these flags, such as `autovacuum`\nand `max_wal_size`, can be set in ways that might compromise the\nstability of the instance or the durability of its data.\n\nFor a complete list of configurable flags and their defaults,\nsee [database flags](/sql/docs/postgres/flags).\n\n### Resource constraints\n\nThe following resource constraints must be avoided to retain SLA coverage:\n\n- **Storage full** : if your disk utilization is consistently high, and automatic storage increase is not enabled, your instance is not properly sized for your workload and may not be covered by the [SLA](/sql/sla).\n- **CPU overloaded** : if your CPU utilization is consistently high, your instance is not properly sized for your workload, and may not be covered by the [SLA](/sql/sla).\n- **Memory overloaded** : if your memory usage is consistently high, your instance is not properly sized for your workload, and may not be covered by the [SLA](/sql/sla).\n- **Transaction ID wraparound** : if your instance runs out of transaction ID and goes offline, this outage is not covered by the [SLA](/sql/sla).\n\nFor more information, refer to the [General best practices](/sql/docs/postgres/best-practices).\n\n\u003cbr /\u003e"]]
