Tabulify supports the Tpc-Ds database benchmark on the following points:
This section shows you how to manage the sub-schema of TPC-DS
tpcds - all TPC-DS tables
tabli data list *@tpcds
tabli data create *@tpcds @targetConnection
tabli data fill *@tpcds @targetConnection
the data-warehouse tables - all tables without the tables that starts with a s (ie without the staging tables)
tabli data list [!s]*@tpcds
tabli data create [!s]*@tpcds @targetConnection
tabli data fill [!s]*@tpcds @targetConnection
The store-sales schema has the store_sales and store_return star schema (a data-warehouse schema).
tabli data list --with-dependencies store*@tpcds
tabli data create --with-dependencies store*@tpcds @targetConnection
tabli data copy --with-dependencies store*@tpcds @targetConnection
This article explains this technic: how to select a star schema
The TPC-DS benchmark does not define the B column (business key) as unique key. Our implementation makes them all unique (except on the item table where the column is unique only with the start and end date)
Why ? Because when using TPC-DS as a sample schema, the data generator will then create data that is consistent with the queries.
For TPC-DS, a business key is neither a primary key nor a foreign key in the context of the data warehouse schema. It is only used to differentiate new data from update data of the source tables during the data maintenance operations.