If you are going to migrate your MySQL workloads to GCP’s managed database service CloudSQL, then you have to keep these points in mind. We have done a lot of CloudSQL migrations. But sometimes it’s not smooth as we thought. Generally, people don’t even think that these thinks will make the replication failure. I listing 3 things that ate our brain and time while migrating to CloudSQL.
1. Server character set:
CloudSQL by default using
utf8 as the server
character set. But it is customizable, we can change it any time.
But still, it’ll mess up your application later. We had a MySQL
server on a VM where the server’s character set was
latin1. We dump the database and restore it to
CloudSQL. While launching the CloudSQL we didn’t set up any
Database flags. So the data restore with
mysql> SHOW SESSION …