Azure Data Factory vs. Oracle Warehouse Builder

In a data pipeline, you will be able to add different kinds of activities for example connect from your on-premise SFTP and move CSV files to storage accounts. As well data factory has its own data flow if you are an ETL developer who experimented with maybe you have worked with SSIS, thus, you will start quickly with this new feature of the data factory.

Incentivized

If you plan to upgrade your databases to newer versions, you need to migrate your Oracle Warehouse Builder jobs to Oracle Data Integrator (fastest and easiest way) or an other ETL tool, because Oracle Warehouse Builder came to an end and does not support newer versions of databases as it is described in statement of direction. There will be no major releases of Oracle Warehouse Builder (latest
release is 11GR2 - 11.2.0.4), but bug resolving and minor releasing will continue.

Incentivized

• Creating ETL and ELT workflows as well as orchestrating and monitoring pipelines without writing any code.
• Hybrid data integration is easily and agilely possible through this software.
• It has lot of various useful components

Incentivized

• Simplified user interface with all required ETL functions
• Flexible and Efficient

Incentivized

• Learning curve for pipeline creation interface.
• Alerting isn't necessarily built in. Had to work around this to meet team needs.
• With GIT enabled, some features can only be done via git, while some need to be done via the portal.

Incentivized

• No good learning material available.
• I didn't see a training course for it.
• It is not easy to learn.

Incentivized

So far product has performed as expected. We were noticing some performance issues, but they were largely Synapse related. This has led to a shift from Synapse to Databricks. Overall this has delayed our analytic platform. Once databricks becomes fully operational, Azure Data Factory will be critical to our environment and future success.

Incentivized

We have not had need to engage with Microsoft much on Azure Data Factory, but they have been responsive and helpful when needed. This being said, we have not had a major emergency or outage requiring their intervention. The score of seven is a representation that they have done well for now, but have not proved out their support for a significant issue

Incentivized

Azure Data Factory fits well into our overall systems architecture where we already utilize largely Azure services and also Microsoft based products in the on-premises environment. I think cost structure is also very competitive with Azure Data Factory. Most services provide a visual interface for designing ETL workflows, but our team found Azure Data Factory's interface more intuitive.

Incentivized

I think that Oracle Warehouse Builder is easier to use the Oracle Data Integrator (ODI). The connections in Oracle Warehouse Builder (OWB) are easier to understand when troubleshooting. Anything that makes troubleshooting easier gets higher marks in my book. ODI wins in the heavy lifting and enterprise solution realm. ODI is much easier to implement at that level. The web interface that can be setup for business users to kick off scenarios is better than the interface that we can give access to in OWB.

Incentivized

• Limiting the amount of data moving up and down from the cloud for cloud-native applications.
• Overall simple to use interface which is actually easier for a first time ETL developer than SSIS.

Incentivized

• OWB allows you to quickly develop even complex ETLs thus saving lots of time for the developers to work on other things. I would say OWB is a very convenient and easy to use tool.

Incentivized