Oracle Autonomous Transaction Processing vs. Azure SQL Database

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

Your upcoming app can be built faster on a fully managed SQL database and can be moved into Azure with a few to no application code changes. Flexible and responsive server less computing and Hyperscale storage can cope with your changing requirements and one of the main benefits is the reduction in costs, which is noticeable.

Incentivized

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

Incentivized

• Maintenance is always an issue, so using a cloud solution saves a lot of trouble.
• On premise solutions always suffer from fragmented implementations here and there, where several "dba's" keep track of security and maintenance. With a cloud database it's much easier to keep a central overview.
• Security options in SQL database are next level... data masking, hiding sensitive data where always neglected on premise, whereas you'll get this automatically in the cloud.

Incentivized

• 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

• One needs to be aware that some T-SQL features are simply not available.
• The programmatic access to server, trace flags, hardware from within Azure SQL Database is taken away (for a good reason).
• No SQL Agent so your jobs need to be orchestrated differently.
• The maximum concurrent logins maybe an unexpected problem.
• Sudden disconnects.
• The developers and admin must study the capacity and tier usage limits https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits otherwise some errors or even transaction aborts never seen before can occur.
• Only one Latin Collation choice.
• There is no way to debug T-SQL ( a big drawback in my point of view).

Incentivized

This is best solution as a DBA one could expect from a service provider and as a cloud service, it removes all your hassles.

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

We give the support a high rating simply because every time we've had issues or questions, representatives were in contact with us quickly. Without fail, our issues/questions were handled in a timely matter. That kind of response is integral when client data integrity and availability is in question. There is also a wealth of documentation for resolving issues on your own.

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

We moved away from Oracle and NoSQL because we had been so reliant on them for the last 25 years, the pricing was too much and we were looking for a way to cut the cord. Snowflake is just too up in the air, feels like it is soon to be just another line item to add to your Azure subscription. Azure was just priced right, easy to migrate to and plenty of resources to hire to support/maintain it. Very easy to learn, too.

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

• Perfect for small and medium databases, being very cost effective.
• As a Platform as a Service, there is no concern about patches, upgrades and end of life.
• Be aware of security and network capabilities. The service cannot run in the VNET as Azure Virtual Machines do.