When i imported the schema SalesLT of the AdventureWorksLT2008R2 database in Quipu ‘something’ happened in the following tables:
Specially the tables with numbers are interesting:
The next step what i’ve done is generating the staging database with the option ‘Generate staging’ and when i executed this option the following changes were discovered in the tables op de metadata database:
Some changes appeared in the already inventoried tables in the Quipu metadata tables. Two extra tables are filled with data:
The last step i’ve executed is generating the datavault model. When i generated the datavault, the following model is a representation of changed number of records in the tables.
There are no new tables used for filling new records, so this seems it concerning the dynamic metadata of generating the data vault. The following things catched my eyes:
- The SQL code is generated from templates stored in the table 'qp_sql_template'.
- There is no sql code in 'qp_sql_step' table for generating ETL/DDL for the datavault in contrast with the staging scheme. May be the code of the staging area is a mistake? Logically it would be best to generate the SQL code right from the metatables and the templates.
Update after comments of The Los Tilos.
The above diagrams have more relationships. In the diagram below relationships are shown better.