Cloud SQL supported engines (MySQL, PostgreSQL, SQL Server) in GCP - Step-by-Step Execution

Process Flow - Cloud SQL supported engines (MySQL, PostgreSQL, SQL Server)

Start: Choose Cloud SQL

↓

Select Database Engine

↓

MySQL

↓

Configure Instance Settings

↓

Deploy Cloud SQL Instance

↓

Instance Ready to Use

This flow shows how you start with Cloud SQL, pick one of the supported engines (MySQL, PostgreSQL, or SQL Server), configure settings, and deploy the instance.

Execution Sample

GCP

gcloud sql instances create my-instance --database-version=MYSQL_8_0

# or

gcloud sql instances create my-instance --database-version=POSTGRES_14

# or

gcloud sql instances create my-instance --database-version=SQLSERVER_2019_STANDARD

Commands to create Cloud SQL instances with different supported database engines.

Process Table

Step	Action	Input	Result	Notes
1	Start Cloud SQL instance creation	gcloud sql instances create	Ready to select engine	Initial command to create instance
2	Select MySQL engine	--database-version=MYSQL_8_0	Instance configured for MySQL 8.0	MySQL engine chosen
3	Select PostgreSQL engine	--database-version=POSTGRES_14	Instance configured for PostgreSQL 14	PostgreSQL engine chosen
4	Select SQL Server engine	--database-version=SQLSERVER_2019_STANDARD	Instance configured for SQL Server 2019 Standard	SQL Server engine chosen
5	Deploy instance	Instance config	Cloud SQL instance deployed	Instance is ready to use
6	Exit	N/A	Process complete	Instance created with chosen engine

💡 Instance deployed with selected database engine, process ends.

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
database_engine	None	MySQL 8.0	PostgreSQL 14	SQL Server 2019 Standard	Selected engine version

Key Moments - 2 Insights

Why do we specify the database engine version during instance creation?

Because Cloud SQL supports specific versions of MySQL, PostgreSQL, and SQL Server, specifying the version ensures the instance runs the correct engine and version as shown in execution_table rows 2-4.

Can we change the database engine after the instance is created?

No, the database engine is fixed at creation time. To use a different engine, you must create a new instance, as indicated by the flow ending after deployment in the concept_flow.

Visual Quiz - 3 Questions

Look at the execution_table, what database engine is selected at Step 3?

A MySQL 8.0

B PostgreSQL 14

C SQL Server 2019 Standard

D No engine selected

💡 Hint

Check the 'Input' and 'Result' columns in execution_table row 3.

At which step does the Cloud SQL instance become ready to use?

A Step 2

B Step 4

C Step 5

D Step 6

💡 Hint

Look at the 'Result' column for when the instance is deployed in execution_table.

If you want to use SQL Server 2019 Standard, which database_engine value will variable_tracker show after selection?

A SQL Server 2019 Standard

B PostgreSQL 14

C MySQL 8.0

D None

💡 Hint

Refer to variable_tracker row for database_engine after Step 4.

Concept Snapshot

Cloud SQL supports three main database engines:
- MySQL (e.g., 8.0)
- PostgreSQL (e.g., 14)
- SQL Server (e.g., 2019 Standard)
You select the engine and version when creating an instance.
The engine cannot be changed after creation.
Use gcloud commands with --database-version flag to specify.

Full Transcript

Cloud SQL lets you create managed database instances using MySQL, PostgreSQL, or SQL Server engines. When you start creating an instance, you must choose which engine and version to use. This choice determines how the instance is configured and what features are available. You cannot change the engine after the instance is created. The process involves selecting the engine, configuring instance settings, and deploying the instance. Once deployed, the instance is ready to use with the chosen database engine.