I noticed that, after creating the cloud SQL instance, the configuration default-settings, costs hundreds of dollars, a little over $500 in my case. This can be problematic for non tech savvy users. The default should be set to the lowest cost possible. Tweaking around the configuration settings, I was able to downgrade and drop the cost down to about $51. which is ten times they default. Oh, and the default is a production instance. Not cool!

I liked the Continuous Database Migration Service Job which manages the migration of MySQL database from on-premises machine to Cloud SQL for MySQL without disrupting the database service. When I decided to update the local database, the Continuous Migration Jobs applied data updates to the Cloud SQL for MySQL instance; Promoting the Cloud SQL instance to a standalone database for reading and writing data completes the migration. I also liked the fact that storage is automatically increased when near capacity while giving the option to provide a specific limit on how large the storage for the instance can automatically grow. Google documentation states that the limit is 64GB. The $300 dollar free trial is a really great incentive to try out the service.

this was part of my traing as an associate cloud developer. I am now studying to be certified

Overall, Google Cloud SQL gave us a convenient way of spinning up database instances very quickly. We use it as backend database for some self-hosted internal apps and it works like a charm.

I like how easy it is to set up, deploy, and manage a PostgreSQL instance using Google Cloud SQL. It saves us time especially when troubleshooting issues thanks to its monitoring/observability features.

I don't have anything I dislike about Google Cloud SQL. It's working great for us so far.

Google Cloud SQL was choose to absorb the replication of data in real time and be able to be performent for user's dashboard, queries...

Easy to set up a cloud sql database, I use GC SQL) with mysql (5 and 8) and postgreSQL. With Mysql, we used it to replicate data inside in real time (from an Oracle Database). With the right configuration the database absorbs the data replication load well and the user was able in the same time to use the data inside Google Cloud SQL (with Datastudio, Google sheets...)

The cost is important when we want to have the high availability... The backup in a instance can be restored only in the instance which was extracted, it can be a problem.

I have 2+ years of experience in Cloud SQL and also I got certified in Google cloud professional Database engineer.

I like some functionalities such as High availability option, Cross-region read replica, Automatic storage increase, Encryption of database (CMEK and Google managed keys), Disaster recovery simulation process, Import and export of DB from one instance to another instance.

1. Having limited database engines.2. Easy way of connection profiles with application is missing.3. Security check is missing in Cloud SQL page.

I use this tool every day and it has become my favorite over other environments I have access to. I think what I like most is its ease of moving large queries.

ease of moving large queries, access to information in sheets and also how easy it's to create jobs with scheduled queries

I think I'ld like more editor customization options at a visual level.

It has been great.

I like that it supports Postgresql, mysql and sql server and is a scalable and server less database so no need to worry about infrastructure setups. Its good for a medium sized Bank or stock exchange.

Its a regional database and not a global one, it can only scale upto a few TB's of data.

Utilizzato per creare una back-up del mio database SQL, facile da utilizzare e sicuro.

Non ho riscontrato problematiche nel breve utilizzo.

J'ai été facturé 133€ pour une utilisation de 3 jours, et quand on parle utilisation c'est créer une table sans requetage dessus c'est un véritable honte

la facturation est démesuré et le service client ne répond pas