Google Cloud SQL is a database-as-a-service (DBaaS) with the capability and functionality of MySQL.
$0
per core hour
Grist
Score 9.9 out of 10
N/A
Grist combines the capabilities of spreadsheets, databases and app builders. Using a familiar spreadsheet interface, information can be organized as a relational database, and dashboards built using drag-and-drop. Solving spreadsheet problems Ensures data is well-structured and stored in one place with no duplication, no spreadsheet-wrangling, no merging documents. Collaboration on sensitive data Data is protected…
$8
per month per user
Pricing
Google Cloud SQL
Grist
Editions & Modules
License - Express
$0
per core hour
License - Web
$0.01134
per core hour
Storage - for backups
$.08
per month per GB
HA Storage - for backups
$.08
per month per GB
Storage - HDD storage capacity
$.09
per month per GB
License - Standard
$0.13
per core hour
Storage - SSD storage capacity
$.17
per month per GB
HA Storage - HDD storage capacity
$.18
per month per GB
HA Storage - SSD storage capacity
$.34
per month per GB
License - Enterprise
$0.47
per core hour
Memory
$5.11
per month per GB
HA Memory
$10.22
per month per GB
vCPUs
$30.15
per month per vCPU
HA vCPUs
$60.30
per month per vCPU
Pro
$8
per month per user
Enterprise
Contact Sales
Offerings
Pricing Offerings
Google Cloud SQL
Grist
Free Trial
Yes
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Pricing varies with editions, engine, and settings, including how much storage, memory, and CPU you provision. Cloud SQL offers per-second billing.
—
More Pricing Information
Community Pulse
Google Cloud SQL
Grist
Features
Google Cloud SQL
Grist
Database-as-a-Service
Comparison of Database-as-a-Service features of Product A and Product B
Does what it promises well, for instance, as a sidecar for the main enterprise data warehouse. However, I would not recommend using it as the main data warehouse, particularly due to the heavy business logic, as other dedicated tools are more suitable for ensuring scalable operations in terms of change management and multi-developer adjustments.
This is well suited to someone (or a team) who are technically minded and have a dataset that they need to be able to use in many ways. It's less appropriate for a team who isn't technically minded and/or don't have the data they need to manipulate. It would be useful for things that you could use a database or spreadsheet for such as CRM, Advertising database, Business tracking, Health tracking etc.
As with other cloud tools, users must learn a new terminology to navigate the various tools and configurations, and understand Google Cloud's configuration structure to perform even the most basic operations. So the learning curve is quite steep, but after a few months, it gets easier to maintain.
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.
Unlike other products, Google Cloud SQL has very flexible features that allow it to be selected for a free trial account so that the product can be analyzed and tested before purchasing it. Integration capabilities with most of the web services tools are easier regarding Google Cloud SQL with its nature and support.
Improved integration with Google Cloud, we have set up some automations with Google Workspace, and we have noticed that the raw data sharing between them is very fast as compared to using some other managed database, not sure why.
Due to some downtime during maintenance, we had to set up a relatively small service which ingested the data while this went down and dumped it when it came back up. So this was a negative impact on our ROI, since now we had to remedy this downtime against the same profit margins
It was cheaper than the legacy aws service since we needed large database instances
It's saved a lot of time in both creating an advertising database and managing it week to week effectively. I had previously created in others that haven't worked, and this does, saving me a good 1 hour weekly, and 5 hours or more each time I had problems with the last ones
Being able to stay on track with this has meant I'm following up at the right time (advertisers) and keeping a professional manner and not losing business due to missed communication
Saving me $ from buying a program like Access (or Airtable monthly) and then the learning curve that that has. This has a much easier learning curve to say the least.