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
Toad Data Point
Score 8.0 out of 10
N/A
Toad Data Point is a cross-platform, self-service, data-integration tool that simplifies data access, preparation and provisioning. It provides data connectivity and desktop data integration, and with the Workbook interface for business users, it provides simple-to-use visual query building and workflow automation.
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 …
TOAD excels at connecting to divergent data sources, but appears geared more to DBAs than to regular query users. Microsoft's offerings excel against Microsoft SQL Server, but sometimes struggle with other data sources.
However, SSMS and VS Code excel at many developer …
Both of these tools offer data extraction and even include SQL components. I noted earlier that RStudio is useful for statistical modeling and data visualization in ways Toad Data Point cannot do. Microsoft Access also has a useful query building window that Toad Data Point is …
I find Toad Data Point easy to use and easy to format and extract data to Excel. The Workbook (new interface) is closely tied to email. Intelligence Central is also closely tied to email. I find this tool essential if your data is stored in different database types or some …
Toad give me more flexibility. Being able to utilize FTP to send data and receive files from external systems is wonderful. Using the automation tool to run different database, file, and system activities has made my day-to-day functions easy. Being able to schedule tasks …
We have tried to use Tableau to try and accomplish a similar set of goals as we do with Toad Data Point. Toad is much more efficient once we have the data connections setup. We are able to easily drag and drop data sources. There are some advantages with Tableau but overall …
I have not used another tool that allows for these seamless connections so it is unfair to rate Tableau and Hyperion against this becuase they have different uses. But if I had to compare, Tableau does not make it as easy to connect to multiple datasources and definitely has …
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.
Toad Data Point is the clear tool of choice if the end-user is interested in reports that are relatively simple to build using SQL code and export to Excel. It is less useful if the analyst also needs to run statistical models on the data and visualize the data for those functions I usually use RStudio or Jupyter Notebook which incorporates those features much more seamlessly.
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
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.
I find Toad Data Point easy to use for both the novice and the experienced business analyst. If all you desire is to access data and create spreadsheets...this is a snap. Toad Data Point actually has cool data analysis features built into it. The newer workflow interface makes automating steps a snap
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.
TOAD excels at connecting to divergent data sources, but appears geared more to DBAs than to regular query users. Microsoft's offerings excel against Microsoft SQL Server, but sometimes struggle with other data sources. However, SSMS and vs code excel at many developer productivity/workflow enhancements. vs code, in particular, has a lively extension system that allows it to be tailored for development/querying/model building/etc. That flexibility comes at a cost - the learning curve is steep for new users. The tradeoff between complexity and power may not be good for some environments/users/situations.
It is the least common denominator - not particularly optimized for our environment or workflows.
Hangs or slowdowns add anywhere from 5% - 7% for projects utilizing large/complicated data setts. (This could be due to other IT-imposed constraints and not entirely due to TOAD.)
Trying to perform some operations requires reading documentation and experimenting in order to figure out the TOAD-specific approaches and commands.
It just works (when we understand it). Updates don't break things and things don't suddenly start behaving differently. Best of all, we don't mysteriously lose functionality.