Consolidated Metadata Column for Database Read Performance

Solution Overview

Problem

Achieving desired read-out performance in database management systems becomes challenging as data volume and complexity increase, particularly in 'big data' environments, where conventional methods like indexes and materialized views are limited in optimizing read-out operations.

Innovation Solution

The solution involves consolidating metadata from multiple data columns into a single consolidated metadata column, allowing for dynamic conversion of non-consolidated database schemes into consolidated ones, and restructuring queries to leverage this consolidated structure for optimized metadata access and storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If metadata for multiple data columns is stored in separate files, then data organization is simplified, but read-out performance deteriorates due to increased I/O operations

Engineering Contradiction:
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent combines metadata for multiple data columns into a single consolidated metadata file, reducing the number of file I/O operations during read-out. This consolidation allows the system to retrieve all necessary metadata in a single read operation rather than multiple separate reads, directly improving read-out performance while maintaining organized data structure.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The consolidated metadata file serves multiple functions: it stores metadata for multiple data columns simultaneously and acts as a universal access point for all metadata retrieval operations. This multi-functional approach eliminates the need for separate metadata files for each data column, reducing I/O overhead while maintaining data organization.

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

2Productivity

If conventional methods like indexes and materialized views are used, then query optimization is provided, but scalability is limited in big data environments

Engineering Contradiction:
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent segments the metadata storage into a consolidated structure that can be independently managed and scaled. By separating metadata from data columns while consolidating metadata access, the system allows metadata to be optimized independently, enabling better scalability in big data environments where metadata management becomes a bottleneck.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a new dimension to metadata management by consolidating metadata into a separate, unified file structure. This dimensional change allows the system to optimize metadata access patterns independently from data storage, providing scalability that conventional row-based or column-based indexing cannot achieve in big data scenarios.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Manufacturing precision

If multiple separate metadata columns are queried, then data specificity is maintained, but query complexity increases

Engineering Contradiction:
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent extracts metadata from multiple separate data column contexts and consolidates it into a single metadata file. This extraction allows queries to access all necessary metadata through a single access point while maintaining the ability to retrieve metadata for specific data columns, reducing query complexity without sacrificing data specificity.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS11681674B2Consolidated metadata in databases
Publication Date: 2023.06.20
  • US11681674B2 patent drawing
  • US11681674B2 patent drawing
  • US11681674B2 patent drawing

AI summary

A database having multiple data columns is disclosed. Whether metadata for the multiple data columns resides in multiple different metadata columns may be determined. If so, the metadata may be consolidated into a single consolidated metadata column.