Fact Staging Table Outer Join Lookup Transformation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

ETL processes for data warehouses face significant performance issues due to the use of lookup transformations, especially when dealing with wide fact tables that have a large number of dimensions, leading to slow processing times and low throughput.

Innovation Solution

Implementing an outer join operation to add foreign keys to records in a fact staging table, while selectively using lookup transformations for non-suitable dimension tables to optimize memory usage and performance, thereby improving the efficiency of data transformation and loading into a data warehouse.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If lookup transformations are used to add foreign keys to fact staging table records, then the transformation process is simple and straightforward, but the processing time increases significantly and throughput decreases for wide fact tables with many dimensions

Engineering Contradiction:
Improveease of transformation processVSAvoidprocessing throughput
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The patent segments the dimension tables into two groups: suitable dimension tables (processed via outer join) and unsuitable dimension tables (processed via lookup transformation). This segmentation allows the system to optimize for throughput on suitable tables while maintaining simplicity for unsuitable tables, resolving the contradiction between ease of transformation and processing productivity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent dynamically determines which dimension tables are suitable for outer join based on characteristics such as the number of dimensions and memory requirements. This dynamic approach allows the system to adapt the transformation method for each dimension table, maximizing throughput for appropriate candidates while falling back to lookup transformations when necessary.

Inventive Principle:
Principle #15Dynamics

2Ease of operation

If lookup transformations are used for all dimension tables, then the process is consistent and easy to implement, but the processing time becomes excessively long for wide fact tables

Engineering Contradiction:
Improveease of implementationVSAvoidtransformation processing time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent divides dimension tables into two categories: those suitable for outer join and those requiring lookup transformation. This segmentation enables the system to reduce processing time for suitable tables while maintaining ease of implementation through lookup transformations for unsuitable tables, thus resolving the contradiction between ease of operation and time loss.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies different transformation methods to different dimension tables based on their specific characteristics. Suitable dimension tables receive the optimized outer join treatment, while unsuitable tables continue to use lookup transformations. This localized approach reduces overall processing time without compromising ease of implementation for the entire system.

Inventive Principle:
Principle #3Local quality

3Productivity

If outer join operation is used for all dimension tables, then processing throughput increases significantly, but memory requirements may be exceeded for large dimension tables

Engineering Contradiction:
Improveprocessing throughputVSAvoidmemory usage
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The patent segments dimension tables based on their suitability for outer join operations, considering memory requirements. By identifying and separating suitable dimension tables from unsuitable ones, the system can apply outer join only where memory resources permit, thereby increasing throughput without exceeding memory capacity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the transformation method parameter based on dimension table characteristics and available memory resources. For dimension tables that fit within memory constraints, outer join is applied to maximize throughput. For larger tables that would exceed memory limits, lookup transformation is used instead, thus resolving the contradiction between productivity and quantity of substance (memory usage).

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS8352458B2Techniques for transforming and loading data into a fact table in a data warehouse
Publication Date: 2013.01.08 ORACLE INT CORP
  • US8352458B2 patent drawing
  • US8352458B2 patent drawing
  • US8352458B2 patent drawing

AI summary

Techniques for transforming records prior to loading the records into a data warehouse in an efficient manner. In one embodiment, instead of using lookup transformations, a database operation such as an outer join operation is used to transform records stored in a fact staging table to add foreign keys to the records corresponding to the dimension tables that are associated with a fact table in a data warehouse to which the records are to be loaded. Since the outer join operation is memory intensive, a determination is made as to which dimension tables from the multiple dimension tables associated with the fact table are suitable, from a performance perspective, for the outer join operation. Only those suitable dimension tables are outer joined to the fact staging table to add the foreign keys for the outer joined dimension tables to the fact staging table records. Lookup transformations may be used to add foreign keys to the fact staging table records for the non-suitable dimension tables. The transformed fact records with the foreign keys may then be loaded into the fact table in the data warehouse.