Azure Synapse Analytics vs. Oracle Exadata

In terms of a well-suited scenario - the Azure Synapse can be used to capture data from multiple sources (especially from onPrem sources apart from Dataverse) and update the transformed data based on the given conditions (eg: refresh data based on the specified date/time ranges). Also, the transformed data can simply be transferred to Azure Data Lake for further processing by utilizing other analytics tools such as PowerBI.

Incentivized

• 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

• The combination of SQL/unstructured data
• Keeping things "complicated, but simple"; [heterogeneous] data formats seen as just SQL tables to business experts used to use Power BI, Excel, and any other traditional SQL-oriented BI tools
• Integration options using "Synapse pipelines", the application of ADFs
• The greatly integrated solution of independent things (Spark MPP cluster, MPP SQL Servers, ADFs) - all sitting under one roof. Great job!
• Integration with super-fast, globally replicated data. I really appreciate the integration of NoSQL databases (namely Core API and Mongo API under Cosmos DB) with purely batch-processed BI data

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

• With Azure, it's always the same issue, too many moving parts doing similar things with no specialisation. ADF, Fabric Data Factory and Synapse pipeline serve the same purpose. Same goes for Fabric Warehouse and Synapse SQL pools.
• Could do better with serverless workloads considering the competition from databricks and its own fabric warehouse
• Synapse pipelines is a replica of Azure Data Factory with no tight integration with Synapse and to a surprise, with missing features from ADF. Integration of warehouse can be improved with in environment ETl tools

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

The data warehouse portion is very much like old style on-prem SQL server, so most SQL skills one has mastered carry over easily. Azure Data Factory has an easy drag and drop system which allows quick building of pipelines with minimal coding. The Spark portion is the only really complex portion, but if there's an in-house python expert, then the Spark portion is also quiet useable.

Incentivized

I am comparing Exadata with the Oracle RAC database experience. In addition to Oracle RAC features, Exadata provides automatic performance optimization through Smart Scan and storage indexes. Deep integration with the Oracle ecosystem and tight coupling with Oracle Enterprise Manager
for monitoring and management. Some downsides of Exadata are: a steep learning curve, concepts like cell offloading, IORM, and flash cache behavior aren’t intuitive initially. Operating
Exadata requires specialized DBA skills.

Incentivized

Microsoft does its best to support Synapse. More and more articles are being added to the documentation, providing more useful information on best utilizing its features. The examples provided work well for basic knowledge, but more complex examples should be added to further assist in discovering the vast abilities that the system has.

Incentivized

They're all part of the Microsoft Azure family, so they are not exactly competitors. They overlap in functionality, but they're targeted at different levels of customers. Azure Data Factory is an excellent stand-alone PaaS (included in Synapse Analytics) for writing, scheduling, and monitoring pipelines. Azure SQL Database (and all the Azure SQL family) is excellent for traditional, SQL-based data warehouses, especially if you're migrating from on-premises. Combined with Azure Data Factory (that can run SSIS packages), it's a perfect solution for a simple path to the cloud. Azure Databricks is effectively the only internal "competitor" to Synapse Analytics but targeted more to a "platform-agnostic" audience. On the other hand, Synapse is more of a proprietary mix of products that are more tightly related to Microsoft technologies.

Incentivized

I couldn’t find all the options listed here, so I’m
summarizing the ones we considered during our evaluation before selecting
Oracle Exadata Service on AWS:


Continuing
to use the Oracle RAC on‑premise database
Running
Oracle Database on AWS EC2
Using
Oracle Database through the AWS RDS service


Since we wanted to retain Oracle RAC capabilities while
achieving high performance and maintaining our presence in the AWS public
cloud, we selected the Oracle Database @AWS Exadata service.

Incentivized

• It definitely has a positive impact on ROI. We are able to use it to generate MORE revenue through predictive analytics and pricing optimization.
• Because of the SQL Data Warehouse design, we're able to set up some self service reporting tools which allow our users to generate reports ad hoc instead of having a full time employee creating these by hand.
• Having visibility into the data is very useful for management to make good business decisions.

Incentivized

• One of the central critical systems was migrated from a large 4-node Oracle RAC running on legacy hardware. This application was experiencing severe performance issues literally causing loss of service for numerous customers. Once it was migrated to a 2-node Exadata server, its average performance improved almost by a level of magnitude, therefore eliminating any signs of application slowness.
• Numerous application databases were migrated to Exadata servers which reduced the overall cost of hardware due to Exadata's price structure.

Incentivized