dbt vs. IBM DataStage

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

Excellent Cloud data mapping tool and easy creating multiple project data analytics in real-time and the report distribution are excellent via this IBM product. Easy tool to provide data visualization and the integration is effective and helpful to migrating huge amounts of data across other platforms and different websites insights gathering.

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

• Very reliable in handling data extraction, data transformation and loading
• Flexibility in connecting to different type of databases, relational or non-relational
• Great features such as parallel processing, hash handling, etc.
• You can also take advantage of its FTP functions, and scheduling features if you need to.

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

• You must understand and know the algorithms, since the wrong use of them generates more time in processing.
• Metadata. You need to develop with connectors, and taking all the Metadata from the menu, all the data that you complete manually, you can't track it.

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

Because it is a flexible tool that can manage many flows and create a strong solution with a interesting use of variables. Easy to scale up as you can copy jobs arleady build and modify them. SQL queries allow to be fast in development and have the pushdown feature, but you loose a little of user friendly look. Metadata management is not strong as a visual feature, but can be determine by job codes.

Incentivized

It could load thousands of records in seconds. But in the Parallel version, you need to understand how to particionate the data. If you use the algorithms erroneously, or the functionalities that it gives for the parsing of data, the performance can fall drastically, even with few records. It is necessary to have people with experience to be able to determine which algorithm to use and understand why.

Incentivized

IBM offers different levels of support but in my experience being and IBM shop helps to get direct support from more knowledgeable technicians from IBM. Not sure on the cost of having this kind of support, but I know there's also general support and community blogs and websites on the Internet make it easy to troubleshoot issues whenever there's need for that.

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

No, it wasn’t my decision to use such an ETL product. I’m just the administrator at this point. I’ve heard there are other products there that are even on cloud support. That is much easier to use, more agile, and user-friendly. That doesn’t have that barrier from user to administrator to the developer standpoint.

• 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

• Not directly related to ROI or cost figures. Only comment here is that IBM tools tend to be more costly than average ETL tools, but it depends on if the company is an IBM shop.
• One positive aspect is the company has had not a need to switch ETL tool for years.
• Upgrading to newer versions of the tool brings flexibility in the tool and up-to-date features in relation to other applications.

Incentivized