OLAP Hierarchy Conversion Using DAGs for Accurate Relational Transfer

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Multidimensional OLAP data is not directly supported by relational algebra or SQL, leading to compatibility barriers and inefficiencies in data exchange between multidimensional and relational databases, resulting in data loss, corruption, and resource wastage during naive copying.

Innovation Solution

Generate a relational table and analytic view in a relational database using summarization hierarchies derived from a multidimensional database, employing a directed acyclic graph (DAG) to handle shared members and resolve conflicts, ensuring optimal population and accurate data transfer.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multidimensional OLAP data is directly copied to relational database, then data exchange between architectures is achieved, but data loss, corruption, and resource wastage occur due to architectural incompatibility

Engineering Contradiction:

Improvedata exchange capabilityVSAvoiddata accuracy

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces an intermediary conversion system that translates multidimensional OLAP data into relational database format through generated relational tables and analytic views. This mediator layer handles the architectural incompatibility by transforming the data representation while preserving data integrity, avoiding direct copying between incompatible systems.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system changes the structural parameters of OLAP data by converting hierarchical dimension relationships into relational schemas with foreign keys and joins. The data is transformed from a multidimensional cube structure into normalized relational tables with specific schema designs that maintain the original data relationships without direct copying.

Inventive Principle:

Principle #35Parameter changes

2Adaptability or versatility

If multidimensional OLAP data is directly copied to relational database, then data exchange between architectures is achieved, but computer resources are wasted due to spurious duplication and unused space

Engineering Contradiction:

Improvedata exchange capabilityVSAvoidcomputer resource efficiency

Core Design Contradiction:

Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent segments the OLAP data into distinct relational tables representing different dimensions and facts. Each table is optimized for its specific purpose, eliminating the need to store redundant copies of entire data cubes. The segmentation allows selective loading of only necessary data portions into the relational database.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Instead of copying entire OLAP cubes, the system creates selective copies of specific dimension hierarchies and aggregation levels as relational tables. This intelligent copying approach replicates only the necessary data structures and relationships required for analytical queries, minimizing resource wastage while maintaining data exchange capability.

Inventive Principle:

Principle #26Copying

3Ease of manufacture

If naive copying method is used for data migration, then data transfer is simple, but data loss, corruption, or system crash may occur due to unstructured dimension data

Engineering Contradiction:

Improvedata migration simplicityVSAvoiddata integrity

Core Design Contradiction:

Ease of manufactureVSReliability

Solution Approach 1:

The system performs preliminary actions by pre-processing OLAP dimension data into structured relational schemas before actual data migration. Dimension hierarchies are pre-converted into normalized tables with defined relationships, and aggregation logic is pre-established through analytic views. This preparation ensures data integrity during the migration process while maintaining relative simplicity.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent replaces the mechanical naive copying process with an intelligent transformation system that uses generated SQL statements and relational schema designs. Instead of simple data duplication, the system automatically generates the appropriate relational structures, joins, and constraints, substituting a robust transformation mechanism for fragile direct copying.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS20250390510A1System and method for conversion of multi-parent representation of relationship to multi-hierarchy one in multi-dimensional analytical databases

Publication Date: 2025.12.25 ORACLE INT CORP

AI summary

Here is database integration in which a relational table and an analytic view are generated and configured in a relational database for acceleration and optimally populated from summarization hierarchies derived from a dimension in a multidimensional database. This approach is a new way to transfer online analytical processing (OLAP) metadata from a multidimensional database to a relational database. Shared members may cause this approach to generate a directed acyclic graph (DAG) that organizes the metadata. The OLAP content generated in the relational database has a novel data topology that is unconventional because relational data normalization strategies such as third normal form (3NF) are avoided. This novel data topology achieves unprecedented data locality of metadata in a relational database. Due to optimization techniques such as graph coloring for detection and resolution of conflicts caused by shared members, the accuracy and speed of the data integration between the two databases is increased.