Reference Tables

Reference tables are relatively small tables that do not need to be distributed and are present on every node in the cluster. Reference tables are implemented via primary-secondary replication to every node in the cluster from the master aggregator. Replication enables reference tables to be dynamic: updates that you perform to a reference table on the master aggregator are quickly reflected on every machine in the cluster.

Data Definition Language (DDL) commands for reference tables can be run from the child, or master aggregator. DDL commands run on a child aggregator are forwarded to the master and propagated from there. Data Manipulation Language (DML) for reference tables can not be run from child aggregators because forwarding is not supported for these commands. See Node Requirements for SQL Commands for more information.

SingleStore DB aggregators can take advantage of reference tables’ ubiquity by pushing joins between reference tables and a distributed table onto the leaves. Imagine you have a distributed clicks table storing billions of records and a smaller customers table with just a few million records. Since the customers table is small, it can be replicated on every node in the cluster. If you run a join between the clicks table and the customers table, then the bulk of the work for the join will occur on the leaves.

Was this Article Helpful?

Thanks For Your Feedback!