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.
N/A
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.
dbt is very flexible and can fit into most data pipelines. This is a pro for most organizations that aren't fully bought into one platform (Google Cloud, etc.)
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.
I actually don't know what the alternative to dbt is. I'm sure one must exist other than more 'roll your own' options like Apache Airflow, say, bu tin terms of super easy managed/cloud data transforms, dbt really does seem to be THE tool to use. It's $50/month per dev, BUT …
Snaplogic is great at the Extraction and Load processes of ETL. It can pull data from anywhere, even behind firewalls. So if you need to get data from various APIs, databases, files, S3, SFTP, etc it is easy to do so. However, it requires special knowledge in order to build …
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 …
Airflow can accomplish the same work as dbt (data build tool), however, dbt's (data build tool) development workflow and UI can open up data transformation and modeling work to non-data engineering teams. Looker might also be able to define data models via LookML with a …
The product is best when combined with the other products of the SAS suite. In particular, it's great for the preparation, analysis and display of the data if it is carried out with the products indicated above. When it is combined with products other than those of the SAS …
SAS Data Management Platform requires third-party drivers to connect to common data sources like SFDC, MS SQL, Postgres. Has almost all features present as compared to the alternatives we evaluated. On top of it, SAS offered statistical transformations and strong metadata …
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.
Because SAS Data Integration Studio is the third party it seems to work equally well with all our systems. That is to say that it doesn't really work better with Microsoft or Oracle but really just seems to work equally well with all of them. It has a very powerful back-end …
Datastage might be the closest one. Being a full ETL tool, it's weird to compare both. Datastage might be more robust for extraction but it lacks the simplicity that the end users need for everyday data extract and analysis.
SAS/Access can work well with MySQL. There are some coding differences between the two, for example how missing values are handled or rules for variable names. MySQL has simpler coding, but if you are familiar with Base SAS, it is not too difficult to learn. With SAS/Access the …
SAS integration is not easy because there are various PAM related modules which require additional vendor involvement. Overall once all integrations are set up, it's a great tool and provides multiple options to users for running their model.
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.
SAS/Access is well suited for companies who need to manipulate and analyze large databases and data-sets. It does the same thing as SQL, and if you already know basic SAS coding it is easier to pick up. SAS/Access works well with analyzing data from multiple data-sources at once, including large databases stored in external and virtual environments like Hadoop. Data can be easily reassembled from relational databases for use by the user. SAS/Access is not necessary if you are only pulling data from one database that you have the physical file for.
SAS supports the main database connection options that allow you to optimize the performance of your extracts and loads.
Simplicity of the syntax for a basic connection.
Ability to configure by an administrator in a BI environment so that all users can benefit from the connection without having to establish it by themselves.
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
It is a versatile product but sometimes difficult to use due to the very close link with the proprietary programming language where specific knowledge is required.
Compared to competitors on the market that offer the same functions for the integration perimeter, it is certainly very expensive.
It is very simple to use when combined with products from the SAS suite, less so it is being used stand-alone or integrated with other well-known brands.
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.
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.
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.
Because SAS Data Integration Studio is the third party it seems to work equally well with all our systems. That is to say that it doesn't really work better with Microsoft or Oracle but really just seems to work equally well with all of them. It has a very powerful back-end that allows us to transform and load our data quickly and efficiently programmer time wise.