Cloud SQL overview

Cloud SQL is a fully managed relational database service for MySQL, PostgreSQL, and SQL Server. This frees you from database administration tasks so that you have more time to manage your data.

This page discusses basic concepts and terminology for Cloud SQL, which provides SQL data storage for Google Cloud. For a more in-depth explanation of key concepts, see the key terms and features pages. For information about how Cloud SQL databases compare with one another, see Cloud SQL feature support by database engine.

Database configurations with Cloud SQL

The following video shows you the benefits of using Cloud SQL. It also demonstrates how to do the following:

  • Create a Cloud SQL instance
  • Create database tables and import .sql data from Cloud Storage
  • Explore data with SQL statements
  • Connect to BigQuery Federated Queries and Data Studio
  • Connect to Compute Engine using the Cloud SQL Auth proxy (previously called the Cloud SQL proxy)

Use cases for Cloud SQL

Cloud SQL provides a cloud-based alternative to local MySQL, PostgreSQL, and SQL Server databases. You should use Cloud SQL if you want to spend less time managing your database and more time using it.

Many applications running on Compute Engine, App Engine and other services in Google Cloud use Cloud SQL for database storage.

What Cloud SQL provides

Cloud SQL offers many services so you don't have to build and maintain them yourself. You can focus on your data and let Cloud SQL handle the following operations:

What is a Cloud SQL instance?

Each Cloud SQL instance is powered by a virtual machine (VM) running on a host Google Cloud server. Each VM operates the database program, such as MySQL Server, PostgreSQL, or SQL Server, and service agents that provide supporting services, such as logging and monitoring. The high availability option also provides a standby VM in another zone with a configuration that's identical to the primary VM.

The database is stored on a scalable, durable network storage device called a persistent disk that attaches to the VM. A static IP address sits in front of each VM to ensure that the IP address an application connects to persists throughout the lifetime of the Cloud SQL instance.

Cloud SQL instance overview:

Database administration

Cloud SQL lets you create and delete databases and database users, but it isn't a database administration tool. There are many database administration tools you can choose from, depending on your database engine, including the following:

Cloud SQL pricing

Cloud SQL pricing varies with your configuration settings, and depends on:

  • How much storage you provision, in GiB per month
  • How many CPUs you select for your Cloud SQL instance
  • How much memory you select for your Cloud SQL instance
  • Where you choose to host your data
  • How much network traffic leaves your instance
  • How many IP addresses you assign and use

Check out some Cloud SQL pricing examples. For more information, see the pricing page.

Connect to a Cloud SQL managed database

Connecting to a Cloud SQL managed database is similar to connecting to a self-managed database. Depending on how you configure it, your Cloud SQL instance has a public IP address (which can be accessed from outside of Google Cloud, using the internet), or a private IP address (which can only be accessed through a Virtual Private Cloud (VPC) network). In addition, Cloud SQL provides different authorization options to control who is allowed to connect to your instance, such as the Cloud SQL Auth Proxy.

For more details on how to connect, authorize, and authenticate to your Cloud SQL instance, see the Connecting Overview page.

Cloud SQL updates

Over the life of a Cloud SQL instance, two kinds of updates can occur:

  • Configuration updates, which are done by the user.
  • System updates, which are performed by Cloud SQL.

Configuration updates

As your database's usage grows and new workloads are added, you might want to update your database configuration to adapt accordingly. Configuration updates include:

  • Increasing compute resources
  • Modifying a database flag
  • Enabling high availability

Although Cloud SQL makes these updates possible with the click of a button, some configuration updates can require downtime.

System updates

Keeping the database instance up and running requires operational effort beyond configuration updates. Servers and disks need to be replaced and upgraded. Operating systems need to be patched as new vulnerabilities are discovered. Database programs need to be upgraded as the database software provider releases new features and fixes new issues. Normally, a database administrator performs each of these updates regularly in order to ensure their systems stay reliable, protected, and up-to-date. Cloud SQL attends to these regular system updates for you, so you can spend less time managing your database and more time developing great applications.

The process Cloud SQL uses to perform system updates varies based on which part of the system is getting updated. In general, Cloud SQL system updates are divided into three categories: hardware updates, online updates, and maintenance.

Hardware updates improve the physical infrastructure, such as swapping out a defective machine host or replacing an old disk. Google Cloud performs hardware updates without interruption to your application. For example, when updating a database server, Google Cloud uses live migration, an advanced technology that reliably migrates a VM from the original host to a new one while the VM stays running.

Online updates enhance the software of the supporting service agents that sit adjacent to the database program on the VM. These updates are performed while the database is up and running, serving traffic. Online updates do not cause downtime for your application.

Maintenance updates apply upgrades to the operating system and the database program. Because these updates require an instance restart, they incur some downtime. For this reason, Cloud SQL lets you schedule maintenance to occur at a time that is the least disruptive to your application.

What's next

Try out one or more of the quickstarts for: