I have a customer who is a significant player in the insurance business who uses the Nexus and Nexus Server to migrate data from Teradata, Oracle, and Netezza to Amazon Redshift and Snowflake. Here is a question they asked me recently.

Good morning Tom,

Quick question.  I have a power user (a very influential power user) that is trying to run a report that connects to both Teradata and Snowflake and then exports the results to Tableau.  He is currently using Denodo for this and it isn’t going very well for him.  He is looking at Alteryx as an alternative.  I was wondering if you thought Nexus would be a good candidate for him to try?

Here is my response:

I appreciate your email immensely. I have included a screenshot of Nexus joining Teradata and Snowflake tables at the bottom of this email (three Teradata tables joining with two Snowflake tables).

Federated queries are my passion for why Nexus exists. However, we always knew that querying all systems and migrating between all systems is key to making Nexus the best federated query tool in the business. Nexus is the perfect tool for joining Teradata and Snowflake together and saving the results on Tableau. We can do this in our current release of Nexus on the client or the Nexus Server.

Business users can use the Nexus Super Join Builder to join tables, views, or Excel worksheets between Teradata and Snowflake. Our approach is special because Nexus will write the SQL automatically for the user, but the user can edit the SQL themselves if they choose.

Even more importantly, the user can choose where to process the join. For example, suppose they join a 10 billion row table from Teradata with a million-row table on Snowflake. In that case, they can make Teradata the hub, and Nexus moves the Snowflake table to Teradata to process the join. On the other hand, if Snowflake has the larger tables, they can make it the hub, and the Teradata tables move to Snowflake, where the join performs. As crazy as what I am about to say may sound, the user can make any system the hub, including their PC or the Nexus Server.

The user then has multiple ways to get the information into Tableau.

  1. They can right-click on the answer set and save it as a TBD (Tableau file) anywhere they want.
  2. They can direct Nexus not to return an answer set but save the results to a table on another database.

And of course, in case we did miss something, we will customize Nexus, so the user has everything they need.

We have put enormous amounts of time and effort into thinking of everything, so I do have other details I am not sharing to save space on this email.

I am happy to provide a demo and free training to get them up to speed.

That was my response to my customer. Here is my conclusion for you.

Denodo and Alteryx do not have the flexibility, power, or performance tuning knowledge to handle joining data across systems like Nexus. Did the CEO of Denodo or Alteryx write 85 books on all major systems? Did anyone at Denodo or Alteryx teach a thousand classes worldwide on 15 different database platforms? Does Denodo and Alteryx query all systems and automatically migrate data at high speeds across all systems? Can Denodo or Alteryx run everything on the user’s laptop or desktop with an option to run all jobs on a Server? Does Denodo or Alteryx allow users to process the join anywhere? No, no, no, no, no!

When you need to join data across all systems please give me a call.

Thank you,


Tom Coffing
CEO, Coffing Data Warehousing
Websites: CoffingDW.com and NexusDataServer.com
YouTube: CoffingDW
Email: Tom.Coffing@CoffingDW.com
Phone: 513 300-0341