Adding Additional Custom Loading and Staging Tables to Integrate in Additional Columns
If certain source tables are required by a customer for data that is currently not in the warehouse and we do not currently have matching load tables for these source tables, they can be added and integrated into the warehouse as custom loadx and stagex tables.
If new loadx tables are created, it is critical that:
• All char/varchar columns from the ERP or wherever are nvarchar columns in the new loadx table.
And
• In the source mapping for that load table, the Unicode mapping option is checked.
Using those custom tables, one of the staging tables must reference existing staging tables to find a match to the business key of the destination dim or fact table.
The new column is added to the dim or fact table, but it does not have a source table or any dummy transformation value set for it.
A post fact or dim table update procedure populates the contents of the new columns, unless for a history table, as per the diagrams.
