Assignment and Exam Content
Cloud SQL
Always Delete your Cloud Resources to Avoid $$ Charges.
Cloud SQL Lab
Cloud SQL Lab Contains – Three major areas below to say complete Lab ☺
A Launch Cloud SQL( MYSQL) Instance
Understand basic concepts – Locations, Performance Read/ Write IOPS etc
B Cloud SQL Advanced Concepts
High Availability , Read Replica , Binary Logging
Exam Tips
3
Always Delete your Cloud Resources to Avoid $$ Charges.
Create SQL Instance Create Instance advanced Maintenance
A • Create Instance with default Configurations - Add read replica, Delete master ,
configurations
Create Cloud SQL Instance
•Provide custom configurations Trigger failover
•Add Instance HA , read Replica etc
Cloud SQL
1 Go To -> STORAGE -> SQL -> Click on Create Instance
You will have three Options
2 1. MYSQL 2nd Generation
2. PostgreSQL
3. MYSQL 1st Generation
- Choose MySQL for this workshop.
- Type : Name of instance Cloud SQL is RDBMS in GCP and you can
launch MySQL and PostgreSQL instances.
- Your Password
MYSQL 1st Generations instance also can be
- Select Region and Zone. created if required.
- And Database version – Click Create. Using can SSH to Virtual Machine where
Cloud SQL instance is running.
Congratulations - Your instance is created now ..
Create SQL Instance Create Instance advanced Maintenance
1 • Create Instance with default Configurations - Add read replica, Delete master ,
configurations
Create Cloud SQL Instance
•Provide custom configurations Trigger failover
•Add Instance HA , read Replica etc
3 Check the status of instance – once its created – Click on
instance and explore multiple options
Explore Overview : Dashboard for all information about your
instance. Like IP, connection name etc.
Explore Connections : See networks options – Currently not
configured to any network so that you can connect this
instance.
Choose your default network and give IP to 0.0.0.0/0 – Open
to all – or instance IP
Check other options like SSL certificates etc.
Explore Users : Try creating users with/without IP address.
Explore Database: Try creating database of your own name.
Explorer Backups: Try Creating backup or configure
automatic backup.
Explorer Replicas : Try Creating Read Replica and failover
Replicas
Create SQL Instance Create Instance advanced Maintenance
1 • Create Instance with default Configurations - Add read replica, Delete master ,
configurations
Create Cloud SQL Instance
•Provide custom configurations Trigger failover
•Add Instance HA , read Replica etc
4
Try exploring other instance level options
Instance Edit : You can edit database instance
You can change Zone of Instance.
You can change instance configuration - Add More CPUs, or
Memory , Size of Storage
Instance Import : You can import external MYSQL data files
Try to change Size of Disk and watch how disk throughput
changes.
Instance Export : export existing database into files.
Try to add Labels to instance.
Observe : What you can change and what you can not.
Instance CLONE : Try to clone instance.
Create SQL Instance Create Instance advanced Maintenance
1 • Create Instance with default Configurations - Add read replica, Delete master ,
configurations
Create Cloud SQL Instance
•Provide custom configurations Trigger failover
•Add Instance HA , read Replica etc
High Availability Configurations
Point in Time recovery
- If you need HA configurations – You can enable it by creating “failover replica”
- If you need – point in time recovery for your database. You need to - If primary instance goes down for any reason – failover replica becomes primary
“Enable binary logging”
instance seamless without you doing it.
- If you want to understand more on point in time recovery – Please
check youtube or google ☺ - Synchronizations is taken care by Google without any problems.
- Once you create failover replica – You can see options for failover
- As one liner : point in time recovery means – you can recover
database on failure (of any kind) without loosing data.
Create SQL Instance Create Instance advanced Maintenance
2 • Create Instance with default Configurations - Add read replica, Delete master ,
configurations
Create Cloud SQL Instance
•Provide custom configurations Trigger failover
•Add Instance HA , read Replica etc
Before Creating next Instance
- Delete Old Instance and Proceed further
Always Delete your Cloud Resources to Avoid $$ Charges.
Create SQL Instance Create Instance advanced Maintenance
2 • Create Instance with default Configurations - Add read replica, Delete master ,
configurations
Create Cloud SQL Instance
•Provide custom configurations Trigger failover
•Add Instance HA , read Replica etc
1
Create SQL Instance with advanced Configurations
Disk Performance
Now go to create instance – Choose following options and create instance
Try changing Type of disk and Size of Disk and see
how
Throughput changes
This means disk performance is dependent on Size
as well as type of disk
High Availability and Read Replica
You can configure read replica at the time of
Click on configure configurations instance creation.
machine type and storage
Now Click on change on instance
Click on configure options
You will get options to choose different instances
Create SQL Instance Create Instance advanced Maintenance
2 • Create Instance with default Configurations - Add read replica, Delete master ,
configurations
Create Cloud SQL Instance
•Provide custom configurations Trigger failover
•Add Instance HA , read Replica etc
Before proceeding further
- Delete Old Instance and Proceed further
Always Delete your Cloud Resources to Avoid $$ Charges.
Cloud SQL : Try Yourself
Create PostgreSQL instance and explore different options
1
2 Create 1st generations Mysql instance and see what options are available (should be limited)
3 Exam Tips
High Availability , Read Replica , Binary Logging , Connection – Very Important for Exam.
Cloud SQL
End of Cloud SQL Assignment
