This page provides information about the settings available for Cloud SQL instances. ## Settings for Cloud SQL for SQL Server | Setting | Modifiable after creation? | Possible values | |---|---|---| | [Instance ID](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#instance-id-2ndgen) | N | Composed of lowercase letters, numbers, and hyphens; must start with a letter. The total length must be 98 characters or less. | | [Region](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#region-2ndgen) | N | The instance's region. For a list of all available regions by Cloud SQL edition, see [Region availability](https://docs.cloud.google.com/sql/docs/sqlserver/region-availability-overview.md.txt). | | [Zone](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#zone-2ndgen) | Y | The possible values depend on the region. | | [Database version](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#database-version-2ndgen) | N | For Cloud SQL Enterprise Plus edition: Console string API enum string SQL Server 2019 Enterprise SQLSERVER_2019_ENTERPRISE SQL Server 2022 Enterprise SQLSERVER_2022_ENTERPRISE SQL Server 2025 Enterprise SQLSERVER_2025_ENTERPRISE For Cloud SQL Enterprise edition: Console string API enum string SQL Server 2017 Standard SQLSERVER_2017_STANDARD SQL Server 2017 Enterprise SQLSERVER_2017_ENTERPRISE SQL Server 2017 Express SQLSERVER_2017_EXPRESS SQL Server 2017 Web SQLSERVER_2017_WEB SQL Server 2019 Standard SQLSERVER_2019_STANDARD SQL Server 2019 Enterprise SQLSERVER_2019_ENTERPRISE SQL Server 2019 Express SQLSERVER_2019_EXPRESS SQL Server 2019 Web SQLSERVER_2019_WEB SQL Server 2022 Standard SQLSERVER_2022_STANDARD SQL Server 2022 Enterprise SQLSERVER_2022_ENTERPRISE SQL Server 2022 Express SQLSERVER_2022_EXPRESS SQL Server 2022 Web SQLSERVER_2022_WEB SQL Server 2025 Standard SQLSERVER_2025_STANDARD SQL Server 2025 Enterprise SQLSERVER_2025_ENTERPRISE SQL Server 2025 Express SQLSERVER_2025_EXPRESS For resource limits of these versions, see [Scale Limits](https://docs.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-2016?view=sql-server-2017#Cross-BoxScaleLimits). | | [Active Directory domain](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#ad-integration) | Y | A drop-down menu for joining a Managed Service for Microsoft Active Directory domain is available. The menu lists any Managed Service for Microsoft Active Directory domains in your project. From the drop-down menu, you can select a domain. For more information, see [Overview of Managed Service for Microsoft Active Directory in Cloud SQL](https://docs.cloud.google.com/sql/docs/sqlserver/ad.md.txt). Additionally, note the [procedures and constraints](https://docs.cloud.google.com/sql/docs/sqlserver/configure-ad.md.txt#integrating-different-project) for integrating with a managed AD domain in a different project. | | [SSL mode](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#ssl-mode) | Y | Enforces/enables SSL as follows: - `ALLOW_UNENCRYPTED_AND_ENCRYPTED`: allows non-SSL/non-TLS and SSL/TLS connections. This is the default value. - `ENCRYPTED_ONLY`: only allows connections encrypted with SSL/TLS. When you use these values, you must set `requireSsl` to a compatible value or unset to avoid the conflict between values of two settings. For more information, see [IpConfiguration](https://docs.cloud.google.com/sql/docs/sqlserver/admin-api/rest/v1/instances.md.txt#ipconfiguration). | | [Server CA mode](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#server-ca-mode) | Y | Lets you configure the server certificate authority (CA) for an instance. You can select one of the following available server CA options: - `GOOGLE_MANAGED_INTERNAL_CA`: this is the default value for instances created with the Google Cloud console, [gcloud CLI](https://docs.cloud.google.com/sdk/gcloud.md.txt), the Cloud SQL Admin API, and Terraform. With this option, an internal CA dedicated to each Cloud SQL instance signs the server certificate for that instance. - `GOOGLE_MANAGED_CAS_CA`: with this option, a CA hierarchy consisting of a root CA and subordinate server CAs managed by Cloud SQL and hosted on Google Cloud Certificate Authority Service (CA Service) is used. The subordinate server CAs in a region sign the server certificates and are shared across instances in the region. For Cloud SQL Auth Proxy connections, to connect to an instance configured with the shared CA option, use the Cloud SQL Auth Proxy version 2.13.0 or later. - `CUSTOMER_MANAGED_CAS_CA`: with this option, you manage the CA hierarchy and the rotation of CA certificates. Before you can create an instance with this option, using CA Service, you create a CA pool in the same region as your instance and at least one CA in that pool. When you create your instance, you specify the CA pool. Your request is delegated to a project-specific service account, which has the permission to use the CA pool. The service account requests a CA from the pool and Cloud SQL uses that CA to sign the server certificate for the instance. For Cloud SQL Auth Proxy connections, to connect to an instance configured with the customer-managed CA option, use the Cloud SQL Auth Proxy version 2.14.3 or later. For more information, see [Certificate authority (CA) hierarchies](https://docs.cloud.google.com/sql/docs/sqlserver/authorize-ssl.md.txt#ca-hierarchies). | | [Automatic server certificate rotation](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#server-cert-rotation) | Y | To enable, set `serverCertificationRotationMode` to `AUTOMATIC_ROTATION_DURING_MAINTENANCE`. To disable, set `serverCertificationRotationMode` to `NO_AUTOMATIC_ROTATION_DURING_MAINTENANCE`. | | [Set edition](https://docs.cloud.google.com/sql/docs/sqlserver/choose-edition.md.txt) | Y | `ENTERPRISE` or `ENTERPRISE_PLUS` > [!NOTE] > **Note:** If you don't specify an edition in the [gcloud CLI](https://docs.cloud.google.com/sdk/gcloud.md.txt) or the Cloud SQL Admin API, then the default Cloud SQL edition is Enterprise (`ENTERPRISE`) for all SQL Server versions. | | [Private IP](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#private-ip) | After it's activated, it can't be deactivated. | Activated or deactivated. | | [Public IP](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#public-ip) | Y | Activated or deactivated. | | [Data Api Access](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#data-api-access) | Y | Activated or deactivated. | | [Authorized networks](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#authorized-networks-2ndgen) | Y | If Public IP is enabled, IP addresses authorized to connect to the instance. You can also specify this value as an IP address range, in [CIDR notation](http://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). | | [Data API access](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#data-api-access) | Y | Allowed or disallowed (default). | | [Data cache](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#data-cache-sqlserver) | Y | Activated or deactivated (default). | | [Machine type](https://docs.cloud.google.com/sql/docs/sqlserver/machine-series-overview.md.txt) | Y | - **For Cloud SQL Enterprise Plus edition instances:**Cloud SQL offers predefined machine types in these machine series: - [N2](https://docs.cloud.google.com/sql/docs/sqlserver/machine-series-overview.md.txt#n2) series. - [Memory-optimized N2](https://docs.cloud.google.com/sql/docs/sqlserver/machine-series-overview.md.txt#memory-optimized-N2) series. - [C4](https://docs.cloud.google.com/sql/docs/sqlserver/machine-series-overview.md.txt#c4) series. - [C4D](https://docs.cloud.google.com/sql/docs/sqlserver/machine-series-overview.md.txt#c4d) series. - **For Cloud SQL Enterprise edition instances:**Cloud SQL offers both predefined and custom machine types in these machine series: - [general purpose - dedicated core](https://docs.cloud.google.com/sql/docs/sqlserver/machine-series-overview.md.txt#gp-dedicated-core) series. - [N4](https://docs.cloud.google.com/sql/docs/sqlserver/machine-series-overview.md.txt#n4) series. [Learn more.](https://docs.cloud.google.com/sql/docs/sqlserver/machine-series-overview.md.txt) | | [Cores](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#cpus-sqlserver) | Y | For information about scale limits for cores, see [Scale limits](https://learn.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-2022?view=sql-server-ver16#scale-limits). | | [Memory](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#memory-sqlserver) | Y | For information about scale limits for memory, see [Scale limits](https://learn.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-2022?view=sql-server-ver16#scale-limits). | | [Disable simultaneous multithreading](https://docs.cloud.google.com/sql/docs/sqlserver/create-instance.md.txt#smt-create-instance) | Y | Configure threads per core for an instance from 2 to 1. To learn more about configuring simultaneous multithreading, see [Simultaneous multithreading](https://docs.cloud.google.com/sql/docs/sqlserver/create-instance.md.txt#smt-create-instance). | | [Storage type](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#storage-type-2ndgen) | N | **SSD** **Google Cloud Hyperdisk Balanced** | | [Storage capacity](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#storage-capacity-2ndgen) | Y (Increase only) | Instances with at least one (unshared) vCPU can have up to 64 TB.

Note that creating or increasing storage capacity to 64 TB might increase latency of common operations, such as backups, dependent on your workload. | | [Google Cloud Hyperdisk settings](https://docs.cloud.google.com/sql/docs/sqlserver/storage-options-overview.md.txt#hyperdisk) | Y | This setting applies only to Cloud SQL Enterprise Plus edition instances that use the C4, or C4D machine series, and to Cloud SQL Enterprise edition instances that use the N4 machine series. **Provisioned IOPS** : 4,000 (default value) **Provisioned throughput** : 170 MiB/s (default value) For more information about Google Cloud Hyperdisk settings, see [Google Cloud Hyperdisk Balanced](https://docs.cloud.google.com/sql/docs/sqlserver/storage-options-overview.md.txt#hyperdisk). | | [Enable automatic storage increases](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#automatic-storage-increase-2ndgen) | Y | **On** (default value) **Off** | | [Data encryption method](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#encryption-2ndgen) | N | **Google-owned and Google-managed encryption key** (default value) **Cloud KMS key** | | [Automatic storage increase limit](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#automatic-storage-increase-limit-2ndgen) | Y | In GBs. `unlimited` in the gcloud CLI or `0` in the Cloud SQL Admin API (the default) means there is no limit (other than the maximum available storage for the instance tier). | | [Backups](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#backups-and-binary-logging-2ndgen) | Y | **On** (default value) **Off** | | [Locations options](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#location) | Y | **Multi-region** (default value) **Region** There is also a drop-down menu with a list of multi-regions when you select **Multi-region** or regions when you select **Region**. | | [Instance deletion protection](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#instance-deletion-protection) | Y | Activated or deactivated. | | [Retain backups after instance deletion](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#retain-backups-after-deletion) | Y | Activated or deactivated. | | [Take a final backup at instance deletion](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#final-backup) | Y | Activated or deactivated. | | [Set the retention period for a final backup](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#final-backup-retention-days) | Y | The retention period for the final backup. This value can can be set to a maximum of 365 days. The default value is 30 days. | | [Enable point-in-time recovery (PITR)](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#pitr) | Y (see [note](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#pitr-note)) | **On** **Off** The default value varies by instance. For more information, see [Use PITR](https://docs.cloud.google.com/sql/docs/sqlserver/backup-recovery/pitr.md.txt). | | [Availability: Single zone](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#single) | Y | **On** (default value) **Off** | | [High availability (regional)](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#ha) | Y | **On** **Off** (default value) | | [Maintenance: Maintenance window](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#maintenance-window-2ndgen) | Y | **Any** (default value) **Day of the week and hour of the day** | | [Maintenance: Maintenance timing](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#maintenance-timing-2ndgen) | Y | **Any** (default value) **Canary** (also **Week 1** (was **Earlier** ) / **Preview** ) **Stable** (also **Week 2** (was **Later** ) / **Production** ) **Week 5** | | [Database flags](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#mysql-flags-2ndgen) | Y | See [Configuring Database Flags](https://docs.cloud.google.com/sql/docs/sqlserver/flags.md.txt). | | [Default collation](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#collation) | N | For a list of supported values, see [sys.fn_helpcollations](https://learn.microsoft.com/en-us/sql/relational-databases/system-functions/sys-fn-helpcollations-transact-sql?view=sql-server-ver16). | | [SQL Server Audit](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#sql-server-audit) | Y | Activated or deactivated. | | [Time zone](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#timezone) | Y | You can set the time zone when you create an instance or edit an instance. If you don't specify a time zone, the instance's time zone is UTC. | Instance ID : The instance ID is the name of the instance. It is used to uniquely identify your instance within the project. Choose an instance name that is aligned with the purpose of the instance when possible. The total length of `project-ID:instance-ID` must be 98 characters or less. You do not need to include the project ID in the instance name. This is done automatically where appropriate (for example, in the log files). > [!IMPORTANT] > **Important:** You should be aware that some resource identifiers (such as project IDs) might be retained beyond the life of your project. For this reason, avoid storing sensitive information in resource identifiers. ...see naming guidelines Region : The Google Cloud region where your instance is located. You can only set the region during instance creation. To improve performance, keep your data close to the services that need it. For more information, see [Instance Locations](https://docs.cloud.google.com/sql/docs/sqlserver/locations.md.txt). Zone : The Google Cloud zone where your instance is located. If you are connecting from a Compute Engine instance, select the zone where the Compute Engine instance is located. Otherwise, accept the default zone. You can edit the instance later to change the zone, if needed. For more information, see [Instance Locations](https://docs.cloud.google.com/sql/docs/sqlserver/locations.md.txt). Cores : The number of CPUs for your instance. Memory : The amount of memory available for your instance. For performance-sensitive workloads such as online transaction processing (OLTP), make sure that your instance has enough memory to contain the entire working set. However, there are other factors that can impact memory requirements, such as number of active connections. Perform load testing to avoid performance issues in production. Database version : Unless you need a capability provided only by a specific version, accept the default database version. For `gcloud` command and REST API usage, see [the reference documentation](https://docs.cloud.google.com/sql/docs/sqlserver/admin-api/rest/v1/SqlDatabaseVersion.md.txt). Storage type : Storage type is determined by the machine type you select for your instance. Each machine type belongs to a specific machine series, and each machine series offers different storage type options. Storage type by machine series: - **C4 machine series**: Google Cloud Hyperdisk Balanced - **C4D machine series**: Google Cloud Hyperdisk Balanced - **Memory-optimized-N2 machine series**: SSD - **N2 machine series**: SSD - **N4 machine series**: Google Cloud Hyperdisk Balanced - **General purpose dedicated core machine series**: SSD For the N2, Memory-optimized-N2, and general purpose dedicated core machine series, choosing **SSD** , the default and only value, provides your instance with SSD storage. SSDs provide lower latency and higher data throughput. For the C4, C4D, and N4 machine series, choosing **Google Cloud Hyperdisk Balanced** , the default and only value, provides a scalable, high-performance storage service. To learn more about Google Cloud Hyperdisk Balanced and its limitations, see [Storage options overview](https://docs.cloud.google.com/sql/docs/sqlserver/storage-options-overview). Active Directory domain : You can [integrate](https://docs.cloud.google.com/sql/docs/sqlserver/configure-ad.md.txt) with Managed Service for Microsoft Active Directory, enabling Windows Authentication for the instance. To integrate, you choose a domain for the instance to join. For more information, see the [Overview of Managed Service for Microsoft Active Directory in Cloud SQL](https://docs.cloud.google.com/sql/docs/sqlserver/ad.md.txt). Server CA mode : (Optional) When you create an instance, you can select the server CA mode for the instance. - `GOOGLE_MANAGED_INTERNAL_CA`: this is the default value. Cloud SQL creates a new self-signed server CA for each instance. - `GOOGLE_MANAGED_CAS_CA`: the instance uses a server CA hierarchy hosted by Certificate Authority Service and the issuing CAs are shared across all instances in the same region. - `CUSTOMER_MANAGED_CAS_CA`: the instance uses a server CA that you create from a CA pool. With this option, you manage the CA hierarchy and the rotation of CA certificates. For more information about these options, see [Certificate authority (CA) hierarchies](https://docs.cloud.google.com/sql/docs/sqlserver/authorize-ssl.md.txt#certificate_authority_ca_hierarchies). Automatic server certificate rotation : Choose whether to enable automatic server certificate rotation for the instance. Automatically rotates the server certificate for your instance during your regularly scheduled [maintenance update](https://docs.cloud.google.com/sql/docs/sqlserver/maintenance.md.txt) or when you [perform self-service maintenance](https://docs.cloud.google.com/sql/docs/sqlserver/self-service-maintenance.md.txt) up to 180 days before the certificate expires. By default, this option is disabled. This feature is available only for instances that are configured with `serverCaMode` as `GOOGLE_MANAGED_CAS_CA` or `CUSTOMER_MANAGED_CAS_CA` only. For more information about rotating Cloud SQL server certificates automatically, see [Enable automatic server certificate rotation](https://docs.cloud.google.com/sql/docs/sqlserver/manage-ssl-instance.md.txt#automatic-server-certificate-rotation-cas). Storage capacity : Choose a capacity to fit your database size. After you have created your instance, you can manually increase the storage capacity by [editing your instance configuration](https://docs.cloud.google.com/sql/docs/sqlserver/edit-instance), or you can [manually shrink your storage capacity](https://docs.cloud.google.com/sql/docs/sqlserver/about-storage-shrink) if it becomes larger than your application needs. Increasing the storage capacity does not cause downtime. The amount of storage capacity allocated for your instance affects the cost of your instance. For more information, see [Storage and Networking Pricing](https://cloud.google.com/sql/pricing#2nd-gen-storage-networking-prices). For read replicas, the storage capacity must always be at least as high as the storage capacity of the primary instance. When a primary instance is resized, all read replicas are resized, if needed, so that they have at least as much storage capacity as the updated primary instance. > [!NOTE] > **Note:** Setting your storage capacity too small without enabling [automatic storage increases](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#automatic-storage-increase-2ndgen) can cause your instance to lose its SLA. [Learn more](https://docs.cloud.google.com/sql/docs/sqlserver/operational-guidelines.md.txt) > > Cloud SQL may override the [enable automatic storage increases](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#automatic-storage-increase-2ndgen) and [automatic storage increase limit](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#automatic-storage-increase-limit-2ndgen) settings to perform critical database maintenance. Enable automatic storage increases : If you enable this setting, Cloud SQL checks your available storage every 30 seconds. If the available storage falls below a threshold size, Cloud SQL automatically adds additional storage capacity. If the available storage repeatedly falls below the threshold size, Cloud SQL continues to add storage until it reaches the maximum of 64 TB. > [!NOTE] > **Note:** Automatic storage increases are permanent, but you can [manually shrink your > storage capacity](https://docs.cloud.google.com/sql/docs/sqlserver/about-storage-shrink) if it becomes larger than your application needs. When you enable automatic storage increases, spikes in storage requirements result in incremental, permanent increases in storage size and cost for your instance. If the instance runs out of available storage, it goes offline, and the [Cloud SQL SLA](https://cloud.google.com/sql/sla) may not cover the outage. The automatic storage increase setting of a primary instance automatically applies to any read replicas of that instance. The automatic storage increase setting cannot be independently set for read replicas. > [!NOTE] > **Note:** When an instance is nearly out of storage capacity, it's automatically stopped to prevent the loss of information. Enabling this setting might prevent such an operation. #### Threshold The threshold size depends on the amount of storage provisioned for your instance: **Google Cloud Hyperdisk Balanced** ``` MAX(5, (provisioned storage) * 5 / 100) The threshold size is rounded up to the nearest whole number. ``` For example, the threshold calculation for a 66 GB instance using Google Cloud Hyperdisk balanced is: ``` MAX(5, (66 * 0.05)) = MAX(5, 3.3) = 5 GB ``` **SSD or HDD** ``` MIN(5 + (provisioned storage)/25, 25) The threshold size is rounded down to the nearest whole number. ``` For example, the threshold calculation for a 66 GB instance using SSD or HDD is: ``` MIN(5 + (66/25), 25) = MIN(5 + 2.6, 25) = MIN(7, 25) = 7 GB ``` #### Amount of storage added For Google Cloud Hyperdisk Balanced, the amount of storage added is 15% of the current provisioned storage, but can't be smaller than 5 GB. This can be calculated using the following: ``` MAX(5, (provisioned storage) * 15 / 100) The threshold size is rounded down to the nearest whole number. ``` For all other storage types, including SSD and HDD, the amount of storage added to the instance is equal to the threshold size, which cannot be larger than 25 GB. #### Considerations for large disks For Google Cloud Hyperdisk Balanced, instances provisioned with storage of more than 100 GB have a minimum possible empty space of 5% of the provisioned capacity. For all other storage types and instances provisioned with storage of 500 GB or more, the threshold size is always 25 GB and the amount of storage added is always 25 GB. As a result, the maximum possible empty space is 50 GB. If you don't manually resize the instance with disk space that's greater than 5 TB, then the disk can remain at 99% capacity even though the instance has empty space. Before an operation that rapidly grows disk space usage, such as a large import or a query that requires a large temp table, manually resize the disk, rather than depend on automatic storage increase to keep up. For Google Cloud Hyperdisk Balanced, storage increases that happen too frequently in a short timespan (4 hours), these increases might be subject to throttling. This might result in an instance running out of available space even though automatic storage increases are enabled and the storage size is below the [automatic storage increase limit](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings#automatic-storage-increase-limit-2ndgen). The file system uses some space internally for file system metadata. This space isn't included in the disk usage metric ([`database/disk/bytes_used`](https://docs.cloud.google.com/sql/docs/sqlserver/admin-api/metrics.md.txt)). For large disks, the reserved space can take 1% to 3% of total disk size, so you might see the automatic storage increase occur before the disk usage reaches the threshold. Data encryption method : By default, your Cloud SQL instance is encrypted with a Google-owned and managed key. If you want to control this key, then use a customer-managed encryption key (CMEK) in Cloud Key Management Service (KMS). Cloud KMS integrates with Cloud SQL. Using Cloud KMS keys gives you control over their protection level, location, rotation schedule, usage and access permissions. In addition, you can use various encryption keys across resources. Using Cloud KMS also lets you track key usage, view audit logs, and control key life cycles. Instead of Google owning and managing the keys that protect your data, you control and manage these keys in Cloud KMS. For more information about CMEKs, see [About customer-managed encryption keys (CMEKs)](https://docs.cloud.google.com/sql/docs/sqlserver/cmek.md.txt). Automatic storage increase limit : If you enable the [automatic storage increase setting](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#automatic-storage-increase-2ndgen), you can provide a specific limit on how large the storage for your instance can automatically grow. Keep in mind that the bigger the size of the instance, the greater the operational latency. Automatic storage increases are permanent unless you [manually shrink your storage capacity](https://docs.cloud.google.com/sql/docs/sqlserver/about-storage-shrink), so this limit can prevent your instance size from growing too large due to a temporary increase in traffic. Keep in mind that when an instance becomes unable to add storage that it needs, the instance likely stops accepting incoming connections and could go offline. By default, there is no limit on automatic storage increases other than the maximum available storage for the instance tier. To set the limit when you create the instance, use the `--storage-auto-increase-limit=INTEGER_VALUE_OF_GB` parameter, as described on the [create instance](https://docs.cloud.google.com/sql/docs/sqlserver/create-instance.md.txt#gcloud) page. The value in GB must be at least the current storage size of the instance (minimum 10 GB) and cannot exceed the maximum storage capacity for the instance. To set the limit on an existing instance, use the same parameter with the `gcloud sql instances patch` command. To remove an existing automatic storage increase limit using the [gcloud CLI](https://docs.cloud.google.com/sdk/gcloud.md.txt), run the `gcloud sql instances patch` command with `--storage-auto-increase-limit=unlimited` (the `--storage-auto-increase-limit` flag doesn't accept `0`): ```bash gcloud sql instances patch INSTANCE_NAME \ --storage-auto-increase-limit=unlimited ``` Setting `--storage-auto-increase-limit=unlimited` removes the custom limit so that storage can automatically increase up to the maximum available storage for the instance tier. In the Cloud SQL Admin API, setting the [`settings.storageAutoResizeLimit`](https://docs.cloud.google.com/sql/docs/sqlserver/admin-api/rest/v1/instances.md.txt#DatabaseInstance.Settings.FIELDS.storage_auto_resize_limit) field to `0` (the default value) removes the limit. The automatic storage increase limit setting of a primary instance automatically applies to any read replicas of that instance. The automatic storage increase limit setting cannot be independently set for read replicas. Automated backups and point-in-time recovery : These options determine if automated backups are performed and if transaction log backups are enabled. Both options add a small performance cost and use additional storage, but are required for the creation of replicas and clones, and for point-in-time recovery. When you select this option, you can also select a timeframe when automated backups occur. Automated backups happen daily, during the time window you choose. At the end of seven days, the oldest backup is deleted. For information about point-in-time recovery, see [Overview of point-in-time recovery](https://docs.cloud.google.com/sql/docs/sqlserver/backup-recovery/pitr.md.txt). For information about replication, see [Replication Options](https://docs.cloud.google.com/sql/docs/sqlserver/replication.md.txt). For information about cloning instances, see [Cloning Instances](https://docs.cloud.google.com/sql/docs/sqlserver/clone-instance.md.txt). > [!NOTE] > **Note:** Enabling or disabling point-in-time recovery causes the instance to be restarted. Existing database connections are closed and must be reopened. > > To speed up instance creation when PITR is enabled, Cloud SQL uses an initial > [instant snapshot](https://docs.cloud.google.com/compute/docs/disks/instant-snapshots.md.txt) for PITR instead of a > [standard backup](https://docs.cloud.google.com/sql/docs/mysql/backup-recovery/backups.md.txt#backup-options). > This snapshot is later converted to a standard backup in the background to support restore > operations. Retention settings for automated backups : The default value for the number of retained backups is 7 but you can change it to any value in the range of 1 to 365. See [Automated backup and transaction log retention](https://docs.cloud.google.com/sql/docs/sqlserver/backup-recovery/backups.md.txt#retention) for more information. Location options : You can choose to store backups in multiple or single regions. **Multi-region** is the default, and the recommended choice because it provides protection against downtime when a region becomes unavailable. Backups are stored in regions that are closest to the instance. You also have the option of selecting a custom location for your backup. Only use this option if required by regulation or if an organization policy requires your backups to be in specific multiple or single regions. See [Custom locations](https://docs.cloud.google.com/sql/docs/sqlserver/backup-recovery/backups.md.txt#custom-backup-location) for more information. Instance deletion protection : Protects an instance against accidental deletion. If this setting is enabled, you must deactivate it before deleting the instance. See [Prevent deletion of an instance](https://docs.cloud.google.com/sql/docs/sqlserver/deletion-protection.md.txt). Retain backups after instance deletion : Retains on-demand and automated backups for an instance after the instance is deleted. For more information about this setting, see [Retained backups](https://docs.cloud.google.com/sql/docs/sqlserver/backup-recovery/backups.md.txt#retained-backups). Take a final backup at instance deletion : Takes a final backup of an instance at time of instance deletion. Use `final-backup-retention-days` to set the retention period for the final backup. If no retention period is set, then the retention period is set to default, which is 30 days. For more information about this setting, see [Take a final backup before instance deletion](https://docs.cloud.google.com/sql/docs/sqlserver/backup-recovery/backups.md.txt#final-backup). Set the retention period for the final backup : Sets the retention period for the final backup. The retention period can be set to a maximum of 365 days. If the `final-backup-retention-days` value isn't set when you enable `final-backup`, then the default retention period of 30 days is used. For more information about this setting, see [Take a final backup before instance deletion](https://docs.cloud.google.com/sql/docs/sqlserver/backup-recovery/backups.md.txt#final-backup). Enable point-in-time recovery : Point-in-time recovery lets you recover from a backup, starting from a specific point in time. For information about point-in-time recovery, see [Overview of point-in-time recovery](https://docs.cloud.google.com/sql/docs/sqlserver/backup-recovery/pitr). Availability: Zonal : Puts your instance and backups in a single zone. When you select this option, there is no failover in the event of an outage. Recommended only for test and development purposes. High availability (regional) : When you select **High availability (regional)** , if there is an outage, your instance fails over to another zone in the region where your instance is located, as long as the failover zone is not having an outage. It is recommended that you select **High availability (regional)** for instances in your production environment. See the [Overview of the high availability configuration](https://docs.cloud.google.com/sql/docs/sqlserver/high-availability). Maintenance window : The day and hour that your maintenance events for the Cloud SQL instance are scheduled. Read replicas don't support maintenance window settings at this time. For more information about maintenance, see [About maintenance on Cloud SQL instances](https://docs.cloud.google.com/sql/docs/sqlserver/maintenance.md.txt#management). Maintenance timing : Your preference about the relative timing of maintenance updates. You can receive your updates one or two weeks after the notification and test your maintenance updates in a test environment before your production instances get the update. You can also choose to receive the maintenance update five weeks ("`week5`") after the notification is sent out. The maintenance timing setting doesn't affect the maintenance version that Cloud SQL applies to your instance. If you don't set the maintenance timing setting, Cloud SQL chooses the timing of updates to your instance (within its maintenance window, if applicable). For more information about maintenance, see [About maintenance on Cloud SQL instances](https://docs.cloud.google.com/sql/docs/sqlserver/maintenance.md.txt#management). Private IP : Configures your instance to use private IP. [Learn more](https://docs.cloud.google.com/sql/docs/sqlserver/private-ip.md.txt). Public IP : If enabled, your instance is allocated a public IPv4 address. When you deactivate Public IP, that address is released; you can reenable Public IP later, but you receive a different IPv4 address. By default, the public IP address is blocked for all addresses. Use [Authorized networks](https://docs.cloud.google.com/sql/docs/sqlserver/instance-settings.md.txt#authorized-networks-2ndgen) to enable access. Data Api Access : Controls whether to allow connections to the instance using the Data API. If activated, you can use [`executeSql`](https://docs.cloud.google.com/sql/docs/sqlserver/executesql-instance.md.txt) to execute statements on the instance. This setting is deactivated by default. Authorized networks : You can add specific IP addresses or ranges of addresses to open your instance to those addresses. For information about configuring IP addresses, see [Configuring IP connectivity](https://docs.cloud.google.com/sql/docs/sqlserver/configure-ip.md.txt). Data API access : This setting controls connectivity to the instance using [Data API](https://docs.cloud.google.com/sql/docs/sqlserver/executesql-instance.md.txt). It's disallowed by default. When allowed, authorized users can use Data API to connect to the instance. For instances with Private IP only, it allows authorized users to connect from the public internet. In the Google Cloud console, configure Data API access by selecting the **Allow Data API** checkbox. For the [gcloud CLI](https://docs.cloud.google.com/sdk/gcloud.md.txt), use the `--data-api-access=ALLOW_DATA_API` flag when you create the instance. Data cache : Data cache is optional for Cloud SQL Enterprise Plus edition instances. Data cache utilizes local SSDs to extend the OS page cache from memory to the SSD tier. Cloud SQL manages this setting. Caching your entire working set provides maximum performance when using data cache. You can use the Google Cloud console, [gcloud CLI](https://docs.cloud.google.com/sdk/gcloud.md.txt), or Cloud SQL Admin API to turn this setting on or off for your Cloud SQL Enterprise Plus edition instances. The following table shows the Data cache size for the various vCPU configurations. The Data cache size is fixed and is not configurable. **Performance-optimized N2 machine family** | Enterprise plus machine type | vCPUs | Memory (GB) | Data cache (GB) | |---|---|---|---| | db-perf-optimized-N-2 | 2 | 16 | 375 | | db-perf-optimized-N-4 | 4 | 32 | 375 | | db-perf-optimized-N-8 | 8 | 64 | 375 | | db-perf-optimized-N-16 | 16 | 128 | 750 | | db-perf-optimized-N-32 | 32 | 256 | 1500 | | db-perf-optimized-N-48 | 48 | 384 | 3000 | | db-perf-optimized-N-64 | 64 | 512 | 6000 | | db-perf-optimized-N-80 | 80 | 640 | 6000 | | db-perf-optimized-N-96 | 96 | 768 | 6000 | | db-perf-optimized-N-128 | 128 | 864 | 9000 | **Memory-optimized machine family** | Machine type | vCPUs | Memory (GB) | Data cache (GB) | |---|---|---|---| | db-memory-optimized-N-4 | 4 | 128 | 750 | | db-memory-optimized-N-8 | 8 | 256 | 1500 | | db-memory-optimized-N-16 | 16 | 512 | 3000 | Activation policy : You change the activation policy by [starting and stopping the instance](https://docs.cloud.google.com/sql/docs/sqlserver/start-stop-restart-instance.md.txt). Stopping the instance prevents further instance charges. Database flags : You can set specific database flags on the Cloud SQL instance. For a complete list of the database flags you can set, see [Configure Database Flags](https://docs.cloud.google.com/sql/docs/sqlserver/flags.md.txt). Default collation : You can set a default collation value for the instance, as described on the [Creating instances](https://docs.cloud.google.com/sql/docs/sqlserver/create-instance.md.txt) page. This collation setting is an instance-level default for sorting rules, case, and accent sensitivity in the instance databases. This collation setting becomes the default for the system databases, too. A collation setting of an instance or database is indicated in the Google Cloud console. You can verify an instance's default collation on the Instance Overview page (available through the [Cloud SQL Instances page](https://console.cloud.google.com/sql/instances)). Additionally, from the Instance Overview page, in the Navigation menu, you can click **Databases** to verify a specific database's collation setting. This collation default is permanent at the instance level but not at the database level. You can change this default with a database administration tool, but only for a specific database that you are creating or updating. You cannot change the collation default for an instance after creating the instance (unless you recreate the instance). If you clone an instance, the default collation carries over to the clone. For a complete list of the supported collation settings, see [Server-level collations](https://docs.microsoft.com/sql/relational-databases/collations/collation-and-unicode-support#Server-level-collations). SQL Server Audit : This setting determines if database auditing is enabled. For more information, see [SQL Server database auditing](https://docs.cloud.google.com/sql/docs/sqlserver/db-audit.md.txt). Time zone : When you [create an instance](https://docs.cloud.google.com/sql/docs/sqlserver/create-instance.md.txt), you can set a time zone for the instance by using the `--time-zone=WINDOWS_TIME_ZONE` parameter. The time zone for the instance can also be set or changed later by [updating the settings of the instance](https://docs.cloud.google.com/sdk/gcloud/reference/sql/instances/patch.md.txt) using the `--time-zone=WINDOWS_TIME_ZONE` parameter. If a time zone is not specified for the instance, the instance's time zone is UTC. A read replica has the same time zone as its primary instance. A clone has the same time zone as its source instance. [When you restore an instance from a backup](https://docs.cloud.google.com/sql/docs/sqlserver/backup-recovery/restore.md.txt), the source instance's time zone setting is applied to the restored instance; the time zone assigned to the backup isn't applied. > [!NOTE] > **Note:**Updating the time zone for your instance can cause inconsistencies in your data. For the available time zone values, see the **Windows time zone column** , under [Time zone mapping](https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-configure-time-zone?view=sql-server-ver16#time-zone-mapping). Alternatively, you can get the available values by using this query: ``` SELECT * FROM sys.time_zone_info; ``` An example of a function for retrieving an instance's time zone is the following: [SYSDATETIMEOFFSET](https://learn.microsoft.com/en-us/sql/t-sql/functions/sysdatetimeoffset-transact-sql?view=sql-server-ver16). The `AT TIME ZONE` function can be helpful for time conversions and more. For information about this function, see [AT TIME ZONE (Transact-SQL)](https://learn.microsoft.com/en-us/sql/t-sql/queries/at-time-zone-transact-sql?view=sql-server-ver16). > [!NOTE] > **Note:** Changing the time zone used by the instance causes the instance to be restarted. Existing database connections are closed and must be reopened. > [!WARNING] > **Warning:** Using an unsupported time zone may cause SQL Server to report incorrect times and [UTC offsets](https://en.wikipedia.org/wiki/UTC_offset). > [!WARNING] > **Warning:** SQL Server 2017 and SQL Server 2019 are now in [extended support](https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2017), and any time zone issues encountered with these versions might not be addressed. For better time zone support, use SQL Server 2022 or later. The following time zones are unsupported for SQL Server 2017: - Alaskan Standard Time - Argentina Standard Time - Atlantic Standard Time - AUS Eastern Standard Time - Bahia Standard Time - Fiji Standard Time - Cen. Australia Standard Time - Central Standard Time - Central Standard Time (Mexico) - E. South America Standard Time - Easter Island Standard Time - Eastern Standard Time - Egypt Standard Time - Iran Standard Time - Jordan Standard Time - Libya Standard Time - Magadan Standard Time - Mountain Standard Time - Morocco Standard Time - N. Central Asia Standard Time - Namibia Standard Time - Norfolk Standard Time - North Korea Standard Time - Pacific Standard Time - Pacific SA Standard Time - Saratov Standard Time - South Sudan Standard Time - Tasmania Standard Time - Tomsk Standard Time - Tonga Standard Time - Turkey Standard Time - Venezuela Standard Time - W. Australia Standard Time The following time zones are unsupported for all major versions, and may cause SQL Server to report incorrect times and UTC offsets if used: - Ekaterinburg Standard Time - Kaliningrad Standard Time - Kamchatka Standard Time - Magallanes Standard Time - Mid-Atlantic Standard Time - North Asia East Standard Time - North Asia Standard Time - Pakistan Standard Time - Paraguay Standard Time - Qyzylorda Standard Time - Russian Standard Time - Sudan Standard Time - Vladivostok Standard Time - Volgograd Standard Time - West Bank Standard Time - Yakutsk Standard Time ## Impact of changing instance settings > [!WARNING] > **Warning:** Moving an instance to a different zone causes instance downtime. The operation involves data replication across zones, meaning downtime duration scales directly with the size of the instance's disk. For most instance settings, Cloud SQL applies the change immediately and connectivity to the instance is unaffected. Changing the number of CPUs or the memory size results in the instance going offline for less than 60 seconds. Changing an instance's zone, configuring the private IP, changing its network, and enabling high availability results in the instance going offline for several minutes. Plan to make these kinds of changes when your service can handle an outage of this duration.
## What's next - Learn how to [edit your instance](https://docs.cloud.google.com/sql/docs/sqlserver/edit-instance.md.txt). - Learn more about [database flags](https://docs.cloud.google.com/sql/docs/sqlserver/flags.md.txt). - Learn how to [authorize IP access for your instance](https://docs.cloud.google.com/sql/docs/sqlserver/authorize-networks.md.txt). - Learn more about [replication options](https://docs.cloud.google.com/sql/docs/replication). - See [pricing](https://cloud.google.com/sql/pricing) for your instance.