top of page
  • tomcoffing

Secrets Behind a 20-Table Join Spanning 20 Systems



The secret behind a non-technical user joining 20 tables across 20 systems in a single query is a modern software architecture we call Nexus.


We provide Nexus software for the user’s desktop or laptop with an option to schedule jobs on a Nexus Server, which is software that companies install on a windows server on-premises or any cloud.


Five major components are required to build a software architecture that can integrate all current and future databases.


The first component allows developers to query all systems. Like all query tools, users can submit SQL and get an answer set, but Nexus takes it much further.


Nexus will write the SQL automatically as the user chooses the tables and columns they want on the report in the Super Join Builder. And once users receive answer sets, they can manipulate the data thousands of ways to deliver additional capabilities usually performed by a database.


The second component is the automatic conversion of table structures (DDL) between all systems. So, for example, if a user wants to convert 10,000 Teradata, Oracle, DB2, or SQL Server tables to Snowflake, Redshift, Synapse, or Google BigQuery, the table and data type conversions will take most companies months, but Nexus does it in seconds.


The third component is a database mover that can automate the building of data-loading scripts, and Nexus has over 400 ways to move data. The automatic converting of table structures combined with the automation of load scripts allows users to move a single table or thousands with the setup taking seconds. For example, as you read this email, thousands of tables are moving to Snowflake, and the setup took minutes.


The fourth component, called the hub, combines the Super Join Builder, automatic conversion, and the database mover that allows users to drop and drag tables or views from any combination of systems. For example, this is how Nexus joined 20 tables from 20 systems in a single query.


But the paradigm shift nobody else has is that users can decide which system processes the join. Nexus tests show that the user can process the 20 tables join on any system, including the user’s PC or a Nexus Server. So, depending on the table sizes, Nexus moves all tables to that system of choice for processing.


Why is the hub important? Imagine you want to join a billion-row table with tables from other systems. It would be best if you made the hub the system where the billion-row table resides so Nexus automatically moves the tables from other systems to the billion-row system.


Imagine joining tables from 10 different systems, but you have a SQL Server system that is no longer used. You can make the SQL Server system the hub, and Nexus moves all tables to SQL Server, and the join happens.


Imagine you want to join two tables from two different systems and expect less than 100,000 rows to return. You make the hub your PC, and Nexus queries both tables separately and brings the answer set back to your PC, where the join happens in the background.


And finally, imagine that you are joining millions of rows across multiple cloud systems. You make the hub the Nexus Server, and the data joins on the Nexus Server at high speeds!


You can process the join on any system that makes sense. And if you change the hub, the Nexus instantly changes the SQL, load utilities, and conversions!


When you have Nexus, you can query, migrate, and join data no matter where it resides!


Watch Nexus perform a 20-table join across 20 database systems in a single query in the video below.





You have data in about 18,000 places, and you know that if you could integrate the right data, you are minutes away from world domination.


You are two minutes away from understanding that migration across all systems is now automated.


It took almost 20 years to make the Nexus software act like a Rosetta stone because of the countless data conversion and load script options, but after testing for almost two decades, we have delivered.


Watch and understand and then migrate and command domination over your database vendors because you can pack up and move instantly.


You are about to see a video of how business users are migrating data to Snowflake with the click of a button in the blink of an eye.


You will also see how users can optionally schedule data movement jobs on the Nexus Server for high-speed transfers.







Please get in touch with me directly to learn more about bringing Nexus into your company.


Tom Coffing, CEO of Coffing Data Warehousing

Email: Tom.Coffing@CoffingDW.com

Call: 513 300-0341 YouTube Channel: https://www.youtube.com/coffingdw






703 views0 comments
bottom of page