dbt vs. Oracle Warehouse Builder

dbt (Data Build Tool) is best suited for doing the data transformation. dbt is just a transformation tool and it is not suitable for building a data pipeline which requires extraction of data and loading. dbt is well suited for SQL based transformation logic and it is less appropriate when transformation logic requires python.

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

• user experience makes it easy to work with SQL and version control
• customer success team and the dbt (data build tool) community help establish best practices
• thorough and clear documentation

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

Incentivized

• Slow load times of the dbt cloud environment (they're working on it via a new UI though)
• More out-of-the-box solutions for managing procedures, functions, etc would be nice to have, but honestly, it's pretty easy to figure out how to adapt dbt macros

Incentivized

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

Incentivized

dbt is very easy to use. Basically if you can write SQL, you will be able to use dbt to get what you need done. Of course more advanced users with more technical skills can do more things.

Incentivized

Matillion is graphical versus dbt, which is SQL code-based (that, of course, is a matter of personal preference and not an objective advantage). The integrated testing, documentation generation, lineage, etc., were additional criteria that led us to choose dbt.

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

• In 3 months we re-wrote the data warehouse (15-20 sources) in dbt with 3 developers.
• We are using it continually for the past year with no issues.
• Sorry, I don't have ROI numbers but the impact was huge.

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