Oracle Exadata vs. Azure SQL Database

• First, get the database on Oracle. If you are in an Oracle stack, it would be much better to use the Oracle products. If you are driving a Ferrari, you wouldn’t put a Mercedes engine in it. If you are writing a query, you cannot rely on other brands. Since I'm an architect, when I look for a product, I look for performance.
• The installation is easy because it comes out-of-the-box and you just start using it.
• Previous to Oracle Exadata, we were using a normal Oracle RAC service. We were just waiting for this product to come out.
• I'm currently writing a data warehouse on Exadata. Before this solution, we were aiming for this to be completed by 8 a.m., when our ETLs would finish. With the help of Exadata's special features, this was reduced to 3 a.m. This solution allows us to bring more data within the same time period. It provides us with more subject areas that provide more reports to our users. Our ETL times reduced to 65%, then to 50%.

Incentivized

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

• Customize-able for specific functionality optimized for combination of online transaction or analytical processing.
• Ability to serve mix workloads with resource management feature enables prioritizing allocation for certain workload.
• Scale-able on-premise with compatibility for cloud deployment offers flexible solution for organization considering to transition from on-premise solution.

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

• Patching can often become quite involved and convoluted. It should be more transparent and straightforward.
• Storage metrics can be difficult and time consuming to obtain.
• Basic administrative functions can be hard to repair when discovered.
• Vendor support can take a while to obtain. Generally several attempts are necessary to reach the right area of vendor expertise.

Incentivized

• 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

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

Oracle Exadata Database Machine had the best performance overall hands down. It clearly beat the competition and we were seeing 1000X improvement on SAP HANA. Oracle Exadata Database Machine beat that without us refactoring our code. To achieve that in HANA, we had to refactor the code somewhat. Now this was for our limited POC of 5 use cases. Given the large number of stored procedures we had in Sybase, we need to capture more production metrics but we are seeing incredible performance.

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

• Single support from a single vendor with both machine and database from Oracle, which is costing us less.
• With Exadata, we need less technical manpower and less technical support. A business transaction with the integrated and centralized database helps us focus on other business needs.
• We don't need to buy additional licenses and Hardware for the next 3 to 5 years.

Incentivized

• 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.