Google Cloud SQL Reviews

35 Ratings
<a href='' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.3 out of 100

Do you work for this company? Learn how we help vendors

Overall Rating

Reviewer's Company Size

Last Updated

By Topic




Job Type


Reviews (1-8 of 8)

Companies can't remove reviews or game the system. Here's why.
December 03, 2020
Cameron Gable | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
We migrated from using on-prem SQL databases to Google's managed MySQL database, CloudSQL, a few years back. It supports all of our relational database needs. Along with other Google-managed data structures, Cloud SQL plays an integral role for our software team and our R&D teams, as it is used as the primary storage for company-wide analysis.
  • It is fully managed, so it gives the user a hands-off approach to relational storage.
  • It has well-built APIs, so it is easy to access in a multitude of ways.
  • It is reasonably easy to use with the Google Cloud Console, so users can access it using a user interface.
  • There is some functionality you cannot do from the console, including, granting and restricting user privileges, among other database management capabilities.
  • It is not trivial to connect to spun up VMS. Currently, we use the Cloud SQL proxy to do so.
Overall, Cloud SQL serves all of the needs we need it to. It can do everything a relational database can do, plus it is completely managed so you don't have to worry about the size of the VM, partitioning, etc.
Customer service has always been helpful and responsive when asked about Cloud SQL specific issues.
Read Cameron Gable's full review
January 22, 2020
Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source
We came to Google Cloud SQL in need of a cloud database solution to house analytic data we collect from various I.T. systems, most importantly our trouble ticketing tool. The goal was a central repository that was easy to manage for our small organization. Our data storage needs are small compared to many organizations.
  • Easy Setup
  • Easy Configuration
  • Tools we use send people elsewhere (AWS especially)
  • Few integrations
Google Cloud SQL was very easy to setup because our institution is already already invested in the Google Cloud Platform. If we had gone with Amazon or Azure, there would have been extra complexity and cost of getting established. The product is a great fit for organizations already invested in GCP. Google offers everything the others do, however third party vendor support is seriously lacking (aka the vendors refer you to other tools like AWS etc).
GCP support in general requires a support agreement. For small organizations like us, this is not affordable or reasonable. It would help if Google had a support mechanism for smaller organizations. It was a steep learning curve for us because this was our first entry into the cloud database world. Better documentation also would have helped.
Read this authenticated review
November 20, 2019
Leonel Quinteros | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
We use Google Cloud SQL with MySQL instances as our primary data storage for all our applications. Performance is great and configuring secure environments is straightforward. We reduced our DB maintenance tasks by 75% and our systems are running better than ever. Automatic backup policies and high availability replication are 1 click away.
  • Configuring a high availability cluster of MySQL or PostgreSQL databases is as easy as choosing how many instances do you want to have. Read-only replicas of the master DB can also be used for read operations relying on the "almost instant" replication mechanisms available.
  • Plays really well with other Google Cloud products, so interoperation with Cloud Functions, Cloud Run, Compute Engine, AppEngine, Kubernetes, VPC, etc. is straightforward and easy to secure, isolating the systems from outside.
  • Uptime SLA is high and maintenance operations are planned and notified in anticipation. Network and CPU performance is really good.
  • Automatic failover on high availability setups will automatically promote a read replica to master almost transparently for the client, so our applications will keep running even if the master DB server crashes.
  • There are no multi-master replication options. That may be a problem on distributed, high load, high performance environments.
  • Not many DB vendors available. MySQL came first, PostgreSQL took longer to be available and just now SQL Server is being offered as Beta.
  • Can get pricey quickly if you need to grow fast and much.
For any serious production setup, where "serious" means aware of the importance of having automatic/secure backups, a good recovery plan, high availability options and managed DB server maintenance, I go with this solution before any self-managed option.

I'd be cautious if I need too much processing power or storage available for my DB. On these cases, I'd first think again about my selected DB architecture, and then analyze some options to calculate ROI of each investment.
I haven't used support for this product since I deployed my first instance. After running it for some years, the docs have always been enough to solve any problem I had encountered.
But speaking about the vendor, Google Cloud support answered well and in an acceptable time to the few issues we needed to get assistance for.
Read Leonel Quinteros's full review
November 30, 2019
Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source
We use Google Cloud SQL for databases that are accessed across multiple servers. These dedicated SQL instances are easy to set up since they don't require a host VM. Not requiring a host VM also allows them to be more flexible and scalable. Settings allow Google Cloud SQL instances to automatically scale size as storage needs increase, and perform scheduled maintenance and backup. In our experience scaling and maintenance do not impact any system functionality.
  • Easy setup - No host VM, no software installation or configuration required.
  • Day to day reliability - Not depending on host VM allows more uptime.
  • Long term reliability - Storage scaling, backups, and maintenance can be scheduled to occur automatically.
  • Secure access is complicated to set up - This is the nature of secure access, but it can be frustrating spending much time simply configuring access.
  • No custom IP - It isn't possible to customize an instance's IP. This makes it harder to replace an instance since a new or clone instance always gets a new IP.
  • Cost tends to increase - This is the nature of cloud hosting, but over time costs creep up as utilization increases.
Google Cloud SQL is a great resource for some purposes, but it's probably overkill for others.
In cases where a database is not always needed (on sometimes, off others), it would be better to use a traditional software installation. If database needs are relatively small, software installation will perform just as well and be easier to support. If a database is only needed in one physical site or a small geographical region, it's better to use a regular server based installation. But as soon as a project has greater database needs, Google Cloud SQL is a great choice. Consider using it if any of these apply:

  • A large amount of data (10+ GB).
  • Decentralized access (many worksites, end-users, etc.).
  • Uptime and reliability are required.
Support for Google Cloud SQL is much like support for any other Google Cloud resource. There is extensive documentation from Google and some from the outside community. Google also provides surprisingly effective on-page tutorials to help when starting out. For anybody who is technically inclined, this will be more than enough to get started, the rest is just good old fashioned database administration.
If personalized support is required, as with all Google Cloud resources, a paid support plan is required. This can be frustrating, but given the uniqueness and complexity of the platform for individual users, this is probably not avoidable.
Read this authenticated review
April 10, 2019
Bhargav Nanekalva | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
Google Cloud SQL is a managed SQL database service for MySQL and PostgreSQL. Since we use MySQL for some of our products, we moved our SQL tables schema and data from VMs to a Google Cloud SQL MySQL instance. This has helped us with simple backups/restorations, upgrades/downgrades, fine-tuning settings, and uptime. This also meant that if we had our MySQL running on a VM alongside other services and someone accidentally restarted/deleted the VM, then there's no need to worry about such situations if we are using the GCP's SQL.
  • It's easy to configure and use.
  • Built-in automatic data backups.
  • High availability instance failover.
  • Support for other open source SQL servers.
  • Lack of better information/documentation for failover configuration.
Google Cloud SQL provides the two most popular open source SQL servers, does everything right, and can be used for most use cases. It can be used for most business applications and at any scale, as Google Cloud SQL can scale very well based on the application needs. It's less appropriate for applications that use a DB other than MySQL and PostgreSQL, and for apps that don't need data persistence.
Read Bhargav Nanekalva's full review
May 22, 2019
Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source
Google Cloud SQL (MySQL) is used as the relational data store for our product. The ability to scale up, have read replicas, and have automatic failover built into the offering are really nice features. The automated backup feature is nice as well. To have 7 days of backups available at any time without having to support the processes necessary to make that happen is great.
  • Automatic failover to another region in case the database goes down.
  • Easily scale the instance up if more processing power or memory is required.
  • Automatic backup validation. The backups are performed on a daily basis within the selected window, however, they are not validated. This means the backup could be reported as successful but ultimately be unusable in a situation where it is needed. We got around this issue by periodically validating on our own by spinning up a box, restoring the backup to the new instance, and then destroying the instance after validation. It's not perfect, but is a good sanity check to make sure our backups are valid in case we do need them.
It is great if you don't want to worry about managing hardware and infrastructure and instead focus your efforts on work directly related to your product's database needs, i.e. schema design, efficient queries, etc. However, if you are dealing with very large data sets, then BigQuery, BigTable, or similar might be better suited for your needs.
Read this authenticated review
October 02, 2017
Kristian Hareland | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Review Source
We have been using it mainly whenever we need structured data.

Use case:
- Historical pricing of products (Archive)
  • Super easy to set up: new instance -> Authorization -> play
  • Automatic backup every night! (Keeps past 7 days as copy as well)
  • Automatic failover, in case your main SQL instance fails, they automatically switch you over.
  • It could be cheaper. Definitely cheaper.
  • It could provide more information about failovers.
  • It could allow you to customize more.
When you need relational storage.
Not when you need warehousing.
Read Kristian Hareland's full review
March 15, 2017
Tyler Longren | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
[We're] using it as the primary database supporting multiple WordPress installations that are running on Google Cloud. It's being used for every site that we currently have on Google Cloud, and are in the process of moving more sites over to this platform. Having everything on Google's infrastructure makes everything easy to manage and Google Cloud SQL is insanely fast.
  • It's insanely fast.
  • Easy integration with Google Cloud hosted services.
  • It's backed by Google's infrastructure, which is always good.
  • Connecting to it for the first time is a little confusing.
  • An interface for interacting with the data would be awesome.
If you're hosting a site on Google Cloud, it only makes sense to make use of Google Cloud SQL for the database, as opposed to running a separate MySQL service on a VM. It's extremely fast and has resulted in a dramatic improvement in page load time across multiple sites.
Read Tyler Longren's full review

Feature Scorecard Summary

Automatic software patching (8)
Database scalability (8)
Automated backups (8)
Database security provisions (8)
Monitoring and metrics (8)
Automatic host deployment (7)

What is Google Cloud SQL?

Google Cloud SQL is a database-as-a-service (DBaaS) with the capability and functionality of MySQL.

Google Cloud SQL Technical Details

Operating Systems: Unspecified
Mobile Application:No