Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://cloud.google.com/sql/docs/editions-intro below:

Introduction to Cloud SQL editions | Cloud SQL Documentation

Stay organized with collections Save and categorize content based on your preferences.

This page describes Cloud SQL editions and key features.

Cloud SQL offers the following editions to support your various business and application needs. Each edition provides different performance and availability characteristics to meet the needs of your applications.

• Cloud SQL Enterprise edition: provides all core capabilities of Cloud SQL and is suitable for applications requiring a balance of performance, availability, and cost.
• Cloud SQL Enterprise Plus edition: provides the best performance and availability to run applications requiring the highest level of availability and performance in addition to the capabilities of the Cloud SQL Enterprise edition.

The following table provides an overview of the features available for each edition:

C4A (For MySQL and PostgreSQL)

C4A machine series (for MySQL and PostgreSQL) (Preview)

Memory-optimized (for SQL Server)

Cloud SQL Enterprise Plus edition is ideal for applications that require maximum performance. Cloud SQL Enterprise Plus edition for SQL Server delivers up to 4x improved read performance compared to Cloud SQL Enterprise edition.

Cloud SQL Enterprise Plus edition offers the following performance enhancements:

• Improved read performance using data cache: Data cache leverages a fast, local SSD to store data pages that are read frequently. For MySQL and PostgreSQL instances, you can get up to three times improvement in read performance compared to reading from a persistent disk. Data cache is an optional feature and can be enabled during instance creation or after the instance has been created.

• Enhanced write performance: Cloud SQL Enterprise Plus edition delivers up to two times the improvement in write latency. This makes it suitable for write-intensive applications requiring low latency and high throughput.

• Engine autotuning: autotune engine configurations to match the capabilities of the underlying instance platform.

• Better performance with two machine families with higher memory per vCPU: to meet the needs of your demanding SQL Server workloads, choose between performance-optimized machines with 1 vCPU:8GB of RAM and memory-optimized machines with 1 vCPU:32GB of RAM.

Cloud SQL Enterprise Plus edition provides the following major availability enhancements:

• Advanced disaster recovery (DR): you can simplify recovery and fallback processes after you perform cross-region failover. With advanced DR, you can:

  • Choose a cross-region disaster recovery (DR) replica

  • Perform replica failover

  • Restore your original deployment by using zero data loss switchover

  For more information, see Advanced disaster recovery (DR) and Use advanced disaster recovery (DR).

• Near-zero downtime: with Cloud SQL Enterprise Plus edition, you can maintain near-zero downtime for your instance when you perform any of the following management tasks:

  • Perform or simulate a planned maintenance update event on a standalone primary instance

  • Enable or disable data cache

  • Scale up the compute size (vCPU, memory) of your Cloud SQL instance as many times you like

  • Scale down the compute size (vCPU, memory) of your Cloud SQL instance once every three hours

    Note: If you scale down your instance more than once during a three-hour period, then only the first scale down event benefits from near-zero downtime. Subsequent scale down events experience regular downtime.

  • Perform an in-place upgrade to Cloud SQL Enterprise Plus edition

  Near-zero downtime is available for Cloud SQL for PostgreSQL and Cloud SQL for MySQL instances.

For more information about Cloud SQL editions pricing, see Cloud SQL pricing.

This section provides answers to frequently asked questions about Cloud SQL editions.

Yes. Cloud SQL Enterprise Plus edition is supported on Cloud SQL for MySQL, Cloud SQL for PostgreSQL, and Cloud SQL for SQL Server.

Cloud SQL for MySQL and Cloud SQL for PostgreSQL instances that you created before July 12, 2023, have become Cloud SQL Enterprise edition instances with no change in features or pricing. Instances created after July 12, 2023 can be either Cloud SQL Enterprise edition or Cloud SQL Enterprise Plus edition.

Cloud SQL for SQL Server instances that you created before August 1, 2024, have become Cloud SQL Enterprise edition instances with no change in features or pricing. Instances created after August 1, 2024 can be either Cloud SQL Enterprise edition or Cloud SQL Enterprise Plus edition.

Cloud SQL Enterprise Plus edition has a new pricing structure. For more information about Cloud SQL pricing, see Cloud SQL pricing.

You can create Cloud SQL Enterprise Plus edition and Cloud SQL Enterprise edition instances in regions where supported using Google Cloud console and gcloud CLI.

Yes, you can. Cloud SQL Enterprise Plus edition and Cloud SQL Enterprise edition provide different levels of database performance availability and data protection capabilities. You can select the Cloud SQL editions that best meets your varying application needs.

By using in-place upgrade, you can upgrade your instances to Cloud SQL Enterprise Plus edition or switch to Cloud SQL Enterprise edition.

You can move your Cloud SQL for MySQL and Cloud SQL for PostgreSQL instances between Cloud SQL Enterprise edition and Cloud SQL Enterprise Plus edition with Database Migration Service using the following two ways:

• Upgrade an instance to Cloud SQL Enterprise Plus edition by using IP allowlists
• Upgrade an instance to Cloud SQL Enterprise Plus edition by using VPC peering

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-14 UTC.

[[["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-14 UTC."],[],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4