Google Cloud SQL is a database-as-a-service (DBaaS) with the capability and functionality of MySQL.
$0
per core hour
Oracle Database
Score 8.3 out of 10
N/A
Oracle Database, currently in edition 23ai, is a converged, multimodel database management system. It is designed to simplify development for AI, microservices, graph, document, spatial, and relational applications.
$0.05
per hour
Pricing
Google Cloud SQL
Oracle Database
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
Oracle Base Database Service - Standard
$0.0538
per hour
Oracle Base Database Service - Enterprise
$0.1075
per hour
Oracle Base Database Service - High Performance
$0.2218
per hour
Standard Edition
Contact Sales
Enterprise Edition
Contact Sales
Personal Edition
Contact Sales
Offerings
Pricing Offerings
Google Cloud SQL
Oracle Database
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.
Easier learning, simple features and settings with a very user-friendly application environment and flexible prices make Google Cloud [SQL] a pioneering option over competitors
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.
We migrated from NoSQL to an Oracle database. One of the reasons was robust backup and recovery options available in the Oracle database, which provide zero data loss. A transactional database like Oracle is a better fit for our use case than NoSQL. On a large scale, deployment was evaluated as a cheaper option than the NoSQL engine. This conclusion came even after considering Oracle license is expensive.
There is a lot of sunk cost in a product like Oracle 12c. It is doing a great job, it would not provide us much benefit to switch to another product even if it did the same thing due to the work involved in making such a switch. It would not be cost effective.
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.
Many of the powerful options can be auto-configured but there are still many things to take into account at the moment of installing and configuring an Oracle Database, compared with SQL Server or other databases. At the same time, that extra complexity allows for detailed configuration and guarantees performance, scalability, availability and security.
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.
1. I have very good experience with Oracle Database support team. Oracle support team has pool of talented Oracle Analyst resources in different regions. To name a few regions - EMEA, Asia, USA(EST, MST, PST), Australia. Their support staffs are very supportive, well trained, and customer focused. Whenever I open Oracle Sev1 SR(service request), I always get prompt update on my case timely. 2. Oracle has zoom call and chat session option linked to Oracle SR. Whenever you are in Oracle portal - you can chat with the Oracle Analyst who is working on your case. You can request for Oracle zoom call thru which you can share the your problem server screen in no time. This is very nice as it saves lot of time and energy in case you have to follow up with oracle support for your case. 3.Oracle has excellent knowledge base in which all the customer databases critical problems and their solutions are well documented. It is very easy to follow without consulting to support team at first.
Overall the implementation went very well and after that everything came out as expected - in terms of performance and scalability. People should always install and upgrade a stable version for production with the latest patch set updates, test properly as much as possible, and should have a backup plan if anything unexpected happens
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.
Because of a rich user base and support for any critical issue, this is one of the best options to choose. In case the project has a TCO issue, it can compromise and choose Postgres as the best alternative. SQL server is also good and easy to code and maintain but performance is not as good as the Oracle
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