The Rosetta Stone, a 2,200-year-old slab of black granite, unlocked the secrets of ancient Egypt, bridging a 1,400-year gap in understanding their written language. Discovered in 1799, it bears the same decree inscribed in three scripts: Greek, Demotic, and Egyptian hieroglyphs. This trifecta became the key for scholars, led by Jean-François Champollion, to decode hieroglyphs, reviving the lost voices of an ancient civilization. A single artifact transformed human history, revealing the art, religion, and daily life of a culture that had long been shrouded in mystery.

In the data industry, where databases do not understand each other’s language, we built a Data Rosetta Stone so every database could instantly convert tables and data types on any database they encounter.

We call our Data Rosetta Stone the Nexus because it queries all systems, migrates data instantly across all systems, and can join data seamlessly across databases.

Because of our Data Rosetta Stone theory, we do federated queries (cross-system joins) better and differently than anyone else.

The video below shows a 20-table join that spans 20 systems, but here is where we are different from any other software company in the world.

We write the SQL for the user and run the SQL for the 20-table join on any system you choose, which we call “The Hub.” For example, if you used the “Hub” drop-down to choose a Teradata system, Nexus would convert the table structures from all other databases to Teradata, change the SQL to Teradata, and then temporarily move the data from all other systems to Teradata. We then run the SQL, get the answer set, and remove the temporary tables.

If you change “The Hub” to Databricks, the foreign tables will be converted to Databricks and moved to the Databricks system, where the SQL will run on a Databricks system.

You can even change “The Hub” to your PC, and Nexus will query all 20 tables separately, bring them back to your PC, and join them in the background!

Nobody allows users to join data across all systems and choose to process the joins where they want because they can’t automatically convert the tables and instantly build data movement scripts.

Our approach is the only one that understands data is complicated and joins need to be processed where it makes the most sense, anywhere the user decides.

Thank you,

Tom

Tom Coffing
CEO, Coffing Data Warehousing
Direct: 513 300-0341
Email: Tom.Coffing@CoffingDW.com
Website: www.CoffingDW.com

Posted in Blog