Page History

...

The EDW 3NF model may be retrofitted from an enterprise modeling tool. Refer to Importing a Data Model for details.

The usual steps for creating an EDW 3NF model are defined below and are covered in this chapter. The steps are:

1. Identify the source reference or transactional data that will constitute the EDW 3NF Table. If the data is sourced from multiple tables ascertain if a join between the source tables is possible, or if one or more intermediate stage (work) tables would be a better option.
2. Using the 'drag and drop' functionality drag the load or stage table that is the primary source of information for the EDW 3NF Table into an EDW 3NF target. Refer to Building an EDW 3NF Table for  for details.
3. If there's only one source table and all the columns from it are being used, you can select the auto-create option to build and load the table. This automatically completes the next four steps. Refer to Building an EDW 3NF Table for details.
4. Add columns from other load and/or stage tables if required. Refer to Building an EDW 3NF Table for details.
5. Create the EDW 3NF Table in the database. Refer to Building an EDW 3NF Table for  for details.
6. Build the update procedure. Refer to Generating the EDW 3NF Update Procedure for details.
7. Run the update procedure and analyze the results.

...

By default, EDW 3NF Tables in WhereScape RED do not have an artificial key (artificial keys can be added manually, refer to EDW 3NF Table Artificial Keys for details.

An artificial key is a unique identifier that can be used to join an EDW 3NF Table record to other EDW 3NF Tables.

When joining EDW 3NF Tables it would be possible to perform the join using the business key. For EDW 3NF Tables that satisfy one of more of the following conditions, joining with business keys could result in slow query times and excessive use of database storage:

...