Filter Ratings and Reviews
Filter 35 vetted Google Cloud SQL reviews and ratings
Reviews (1-8 of 8)
Companies can't remove reviews or game the system. Here's why.
December 03, 2020
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.
January 22, 2020
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
November 20, 2019
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.
November 30, 2019
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 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 (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.
October 02, 2017
We have been using it mainly whenever we need structured data.
Use case:
- Historical pricing of products (Archive)
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.
March 15, 2017
[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.
Google Cloud SQL Scorecard Summary
Feature Scorecard Summary
What is Google Cloud SQL?
Google Cloud SQL is a database-as-a-service (DBaaS) with the capability and functionality of MySQL.
Categories: Database-as-a-Service (DBaaS)
Google Cloud SQL Technical Details
| Operating Systems: | Unspecified |
|---|---|
| Mobile Application: | No |