dbt is an SQL development environment, developed by Fishtown Analytics, now known as dbt Labs. The vendor states that with dbt, analysts take ownership of the entire analytics engineering workflow, from writing data transformation code to deployment and documentation. dbt Core is distributed under the Apache 2.0 license, and paid Teams and Enterprise editions are available.
$0
per month per seat
SAS Data Management
Score 8.0 out of 10
N/A
A suite of solutions for data connectivity, enhanced transformations and robust governance. Solutions provide a unified view of data with access to data across databases, data warehouses and data lakes. Connects with cloud platforms, on-premises systems and multicloud data sources.
If you can load your data first into your warehouse, dbt is excellent. It does the T(ransformation) part of ELT brilliantly but does not do the E(xtract) or L(oad) part. If you know SQL or your development team knows SQL, it's a framework and extension around that. So, it's easy to learn and easy to hire people with that technical skill (as opposed to specific Informatica, SnapLogic, etc. experience). dbt uses plain text files and integrates with GitHub. You can easily see the changes made between versions. In GUI-based UIs it was always hard to tell what someone had changed. Each "model" is essentially a "SELECT" statement. You never need to do a "CREATE TABLE" or "CREATE VIEW" - it's all done for you, leaving you to work on the business logic. Instead of saying "FROM specific_db.schema.table" you indicate "FROM ref('my_other_model')". It creates an internal dependency diagram you can view in a DAG. When you deploy, the dependencies work like magic in your various environments. They also have great documentation, an active slack community, training, and support. I like the enhancements they have been making and I believe they are headed in a good direction.
When data is in a system that needs a complex transformation to be usable for an average user. Such tasks as data residing in systems that have very different connection speeds. It can be integrated and used together after passing through the SAS Data Integration Studio removing timing issues from the users' worries. A part that is perhaps less appropriate is getting users who are not familiar with the source data to set up the load processes.
SAS/Access is great for manipulating large and complex databases.
SAS/Access makes it easy to format reports and graphics from your data.
Data Management and data storage using the Hadoop environment in SAS/Access allows for rapid analysis and simple programming language for all your data needs.
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
The main negative point is the use of a non-standard language for customizations, as well as the poor integration with non-SAS systems. However, there is no doubt that it is a high-performance and powerful product capable of responding optimally to certain requirements.
With SAS, you pay a license fee annually to use this product. Support is incredible. You get what you pay for, whether it's SAS forums on the SAS support site, technical support tickets via email or phone calls, or example documentation. It's not open source. It's documented thoroughly, and it works.
Most ETL pipeline products have a T layer, but dbt just does it better. The transformation is on steroids compared to the others. Also, just allows much more Adhoc solutions for very specific projects. Those ETL tools are probably better on the T part if you don't need too many transforms - also dbt is pretty much free dependent on how you work it, also extremely scalable.
Because of ease of using SAS DI and data processing speed. There were lots of issues with AWS Redshift on cloud environment in terms of making connections with the data sources and while fetching the data we need to write complex queries.