Coherent Data Identification for Database Table Development

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database development methods focus on optimizing data storage and reporting, but lack a standardized approach for creating core database table structures that facilitate data sharing across databases, leading to isolated and non-integrated data systems.

Innovation Solution

A coherent data identification method that classifies data items and groups them into unified reference data entities, allowing for the creation of standardized core database tables that can be shared across multiple databases, using a framework that includes data item classification, universal reference data identification, data context analysis, and data normalization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If data normalization rules are applied to minimize data storage requirements, then data storage efficiency is improved, but data retrieval speed deteriorates

Engineering Contradiction:
Improvedata storage requirementsVSAvoiddata retrieval speed
Core Design Contradiction:
Quantity of substanceVSSpeed

Solution Approach 1:

The patent segments the database into two distinct types: normalized OLTP databases for transactional processing and data warehouses for reporting. This segmentation allows each database type to be optimized for its specific function, resolving the contradiction between storage efficiency and retrieval speed by applying normalization only where needed for minimal storage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies data de-normalization to the OLTP databases to improve retrieval speeds for complex reports, while maintaining normalization in data warehouses for optimal storage efficiency. This inversion of the traditional approach allows simultaneous optimization for both storage and retrieval based on operational requirements.

Inventive Principle:
Principle #13The other way round (Inversion)

2Speed

If data warehouse design methodology is used to improve report generation speed, then data retrieval speed is improved, but data storage requirements increase due to data redundancy

Engineering Contradiction:
Improvereport generation speedVSAvoiddata storage requirements
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The patent separates reporting functions into a dedicated data warehouse component that receives data from normalized OLTP databases. This segmentation allows the data warehouse to handle redundancy intentionally for improved report generation, while the source OLTP databases maintain normalization for efficient storage and transaction processing.

Inventive Principle:
Principle #1Segmentation

3Ease of manufacture

If individual database tables are developed independently based on functional needs, then ease of manufacture is improved, but data integration capability deteriorates

Engineering Contradiction:
Improvedatabase table developmentVSAvoiddata sharing capability
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent introduces a universal reference data model framework that provides standardized core database table structures (such as customer, product, order tables) that can be shared across multiple databases. This universality maintains ease of independent table development while enabling data integration and sharing through common reference structures.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS7979475B2Coherent data identification method and apparatus for database table development
Publication Date: 2011.07.12 MACK ROBERT
  • US7979475B2 patent drawing
  • US7979475B2 patent drawing
  • US7979475B2 patent drawing

AI summary

A method, apparatus, and system for configuring, designing, and/or implementing database tables is detailed that provides a framework into which a remainder of database tables are developed. Also detailed is a method to develop this framework of database tables. This so developed framework provides a platform for integrating data from multiple databases. A method is also provided for maintaining and managing master data as a single source of reference data to multiple databases that are based upon this framework.