Co-Founder at a tech services company with 11-50 employees
Real User
Top 5
Nov 6, 2025
We have set up automated patch management for Google Cloud SQL, and it does on a daily basis what needs to be done, so it is pretty good overall for maintaining our database security.
The pricing will fall on the lower side, slightly, almost equal to AWS, and cheaper than Azure. Google Cloud SQL's initial credits and the availability of some boilerplate applications and plugins have boosted some productivity.
When it comes to pricing and licensing for Google Cloud SQL we obtain licenses separately from third-party vendors for our application, while our database uses community-source licensing. The solution is paid for on a monthly basis.
The pricing is interesting. For the enterprise edition, it was almost three times the cost of the standard edition. There should be some more clarity on that. It was not very clear why it's so much more or what the differences are. It requires better documentation.
The licensing is charged yearly, however, I don't manage the cost of the cloud in my company. I only work with Atlassian products. We are users of GCP for our instance. When I work with data in Google Cloud, our data people say the cost is not a problem. I can make a dump of databases daily and store extractions in buckets, for example, every day, full data, all days. And it's not a problem, cost-wise.
The advice I would give before starting up is to have a small interactive introductory session with some domain experts because even though it looks quite similar to MySQL and all the other SQL solutions out there, Google Cloud SQL lets me do a lot more. And it offers a lot of perks if you know how exactly to handle the product. So even if it is with a small, introductory session of two hours or three hours long, where the experts tell me that, "Hey, this is the whole scope of this solution or the product but it will be scaled up," it will help the end-users a lot because the documentation itself is not that extensive.
It's really cheap. It wouldn't be more than, I believe it's around 50 euro per month for running a cloud SQL. There aren't any additional costs that I'm aware of.
Google Cloud SQL provides a fully managed database service underscoring ease of use, scalability, and integration with Google Cloud Platform services.This platform facilitates database operations from automated backups to high availability, supporting databases like Postgres and MySQL. Its intuitive design eases management, while robust features like multi-region support and automatic scaling cater to developers seeking efficient infrastructure management without the burden of extensive...
We have set up automated patch management for Google Cloud SQL, and it does on a daily basis what needs to be done, so it is pretty good overall for maintaining our database security.
The cost is expensive, especially for services like BigQuery, which charge based on query operations. We pay as we use, with no fixed cost.
Google Cloud SQL is competitively priced compared to other services like RDS from Amazon.
The pricing will fall on the lower side, slightly, almost equal to AWS, and cheaper than Azure. Google Cloud SQL's initial credits and the availability of some boilerplate applications and plugins have boosted some productivity.
The solution is expensive.
While the platform’s pricing may be higher, it aligns with industry standards, considering the quality of service and features provided.
It is not expensive, especially considering the significant reduction in database management time.
When it comes to pricing and licensing for Google Cloud SQL we obtain licenses separately from third-party vendors for our application, while our database uses community-source licensing. The solution is paid for on a monthly basis.
The solution is affordable. I rate it a six out of ten. We have a monthly license.
You need to pay extra costs for backup and replication.
The pricing is interesting. For the enterprise edition, it was almost three times the cost of the standard edition. There should be some more clarity on that. It was not very clear why it's so much more or what the differences are. It requires better documentation.
From a financial perspective, Google Cloud SQL is on the cheaper side.
The is no license required.
The licensing is charged yearly, however, I don't manage the cost of the cloud in my company. I only work with Atlassian products. We are users of GCP for our instance. When I work with data in Google Cloud, our data people say the cost is not a problem. I can make a dump of databases daily and store extractions in buckets, for example, every day, full data, all days. And it's not a problem, cost-wise.
The advice I would give before starting up is to have a small interactive introductory session with some domain experts because even though it looks quite similar to MySQL and all the other SQL solutions out there, Google Cloud SQL lets me do a lot more. And it offers a lot of perks if you know how exactly to handle the product. So even if it is with a small, introductory session of two hours or three hours long, where the experts tell me that, "Hey, this is the whole scope of this solution or the product but it will be scaled up," it will help the end-users a lot because the documentation itself is not that extensive.
It's really cheap. It wouldn't be more than, I believe it's around 50 euro per month for running a cloud SQL. There aren't any additional costs that I'm aware of.
The pricing is very much an important factor as to why we use this solution.