Let's load a puzzles dimension along with the history of the changes in puzzle attributes:
js
as Connection.SELECT pro_code , man_code , pro_name , pro_theme FROM products WHERE pro_type LIKE 'PUZZLE'
Date
field named changedate
. As Format type dd/MM/yyyy
, and as Value, type 01/10/2009
. dw
. lk_puzzles
. id
as Technical key field. Use table maximum + 1
. version
. changedate
. start_date
. end_date
. js_dw
database and do a preview of the lk_puzzles
table.You loaded the puzzle dimension with the name and theme of the puzzles you sell. The dimension table has the usual columns for a dimension—technical id (field id
), fields that store the key fields in the table of the operational database (prod_code
and man_code
), and columns for the puzzle attributes (name
and theme
). It also has some extra fields specially designed to keep history.
When you ran the transformation, all records were inserted in the dimension table. Also a special record was automatically inserted for unavailable data.
So far, there is nothing new except for a few extra columns with dates. In the next tutorial, you will learn more about those columns.
18.119.142.232