Normalized Tables Overview
  
Normalized Tables Overview
A Normalized Table is a data warehouse object used to build third normal form enterprise data warehouses. In QAD Data Warehouse Designer, normalized objects have many of the code generating attributes of stage, dimension and fact tables. Third normal form enterprise data warehouses can be thought of as a source system for star schema data marts. Alternatively, they may be reported off directly by users and reporting tools. Normalized Tables can be considered either reference or transactional in nature.
A Normalized Table is built from the Data Warehouse connection. Unless you are retrofitting an existing system, Normalized Tables are typically built from one or more load or stage tables. The normalized model may be retrofitted from an enterprise modeling tool. See Importing a Data Model (on page 962) for more details.
The usual steps for creating a normalized model are defined below and are covered in this chapter. The steps are:
Identify the source reference or transactional data that will constitute the Normalized 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.
Using the 'drag and drop' functionality drag the load or stage table that is the primary source of information for the Normalized Table into a normalized target. See Building a Normalized Table (on page 393).
If there's only one source table and all of 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. See Building a Normalized Table (on page 393).
Add columns from other load and/or stage tables if required. See Building a Normalized Table (on page 393).
Create the Normalized Table in the database. See Building a Normalized Table (on page 393).
Build the update procedure. See Generating the Update Procedure (see "Generating the Normalized Update Procedure" on page 398).
Run the update procedure and analyze the results.
If necessary, modify the update procedure or create a custom procedure.