Database Table Classification for Data Warehouse Processing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current data warehouse systems face challenges in efficiently processing and analyzing multi-dimensional data due to the complexity of managing and integrating various database tables and OLAP cubes, which hinders user-friendly and efficient data processing and analysis.

Innovation Solution

The system introduces a classification mechanism for database tables and OLAP cubes, allowing users to assign them to predefined classes through a mapping table, enabling efficient data processing by merging tables with the same entity type and mapping OLAP cubes to specific classes for transactional data processing, thereby simplifying data access and processing for both experts and non-experts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If database tables and OLAP cubes are managed without classification, then the system maintains flexibility in data structure, but the complexity of managing and integrating various database tables and OLAP cubes increases

Engineering Contradiction:

Improvecomplexity of managing and integrating database tables and OLAP cubesVSAvoidflexibility in data structure

Core Design Contradiction:

Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent segments database tables and OLAP cubes into distinct classes based on their entity types and functional characteristics. This segmentation allows the system to manage different types of data structures through standardized class definitions, reducing the overall complexity of integration while preserving the flexibility of individual table designs within their respective classes.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces a mapping table as an intermediary component that connects database tables and OLAP cubes to their corresponding classes. This mapping mechanism serves as a mediator that simplifies the integration process by providing a standardized interface between diverse data structures and the OLAP processing system, thereby reducing management complexity without constraining data structure flexibility.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of operation

If users manually select and integrate database tables for processing, then the system maintains control over data selection, but the ease of operation for non-expert users deteriorates

Engineering Contradiction:

Improveease of operation for non-expert usersVSAvoidcomplexity of data processing stages

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The patent creates universal class definitions that can accommodate multiple database tables with the same entity type. This universality allows non-expert users to select data for processing simply by choosing a class rather than manually configuring each table, significantly improving ease of operation while the system handles the complex integration logic in the background.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system implements self-service functionality where the classification mechanism automatically identifies and groups database tables into appropriate classes based on their entity types. This automation reduces the operational burden on users, allowing them to perform complex data processing tasks without needing to understand the underlying integration complexity.

Inventive Principle:

Principle #25Self-service

3Productivity

If all database tables are processed individually, then the system maintains precision in data handling, but the productivity of data processing deteriorates

Engineering Contradiction:

Improveproductivity of data processingVSAvoidprecision in data handling

Core Design Contradiction:

ProductivityVSMeasurement precision

Solution Approach 1:

The patent merges database tables that belong to the same class into unified processing units. This merging approach significantly improves productivity by allowing the system to process multiple tables simultaneously through a single OLAP cube configuration, while the class-based structure ensures that data handling precision is maintained through consistent processing rules applied to all tables within each class.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS8214321B2Systems and methods for data processing

Publication Date: 2012.07.03 SAP SE

AI summary

Data processing methods and systems are provided. The data processing methods and systems may include providing a set of database tables in a data warehouse, each one of the database tables being assigned to an entity type and storing entities of its entity type, providing at least one application program for processing of classes of database tables, assigning at least one of the database tables to each one of the classes of database tables of the application program, and processing entities stored in the assigned database tables by the application program.