Google Cloud SQL vs. Oracle Autonomous Transaction Processing

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.

Incentivized

If your company's value is not increased by maintaining databases, you should use the ATP.

• It has a easily and user understandable interface which provides it every necessary feature to come up with.
• It's backend is very strong that can help us to run big quieres without any hesitation.
• It's integration with other tools are one of the powerful feature which makes it more suitable to use.

Incentivized

• Quick and simple to deploy (less than 5 steps to create a new instance)
• No administrative tasks (backup, re-sizing) required

Incentivized

• Increasing support for more database engines may enable a wider range of application needs to be met.
• Implementing and updating cutting-edge security features on a constant basis.
• Streamlining and enhancing the tools for transferring data to Google Cloud SQL from on-premises databases or other cloud providers.

• Connectivity between ATP and Oracle Kuberentes Engine cluster seems to drop randomly
• The ATP could come in an even smaller shape as the smallest shape is already quite big . But if must be more than always free, as that version does have connectivity limitations about 20 connections

It fits the current needs and bandwith of out lean organization.

Incentivized

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.

Incentivized

You get almost all the features of Oracle Database, including the ability to deploy APEX applications, without having to worry about system, storage or database configuration and maintenance, backups, etc. Also, you can start for free and move up adding resources as you need.

Incentivized

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.

Incentivized

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.

Incentivized

Both Azure SQL Database and Oracle Autonomous Transaction Processing offer a powerful and robust database platform. The advantage of Autonomous Transaction Processing is the ability to host APEX applications for free and without any special/complicated deployment or configuration process. Having a rapid development environment embedded for free was the main advantage for choosing Oracle as my cloud database provider.

Incentivized

• 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

Incentivized

• Approx 100 times faster spin up than manual setup of an Oracle DB
• 3h annual maintenance for big version releases (18c to 19c) compared to est. 500h annual maintenance with manual database updates