Sparse Index Table for Low-Frequency Data Retrieval

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Large databases face inefficiencies in querying and retrieving low-frequency data, leading to increased processing time and resource utilization, which impedes analysis and decision-making processes.

Innovation Solution

Implementing an index table that maintains sparse indices for low-frequency data, allowing the database system to directly retrieve specific records without scanning the entire data table, thereby accelerating data retrieval and reducing computational expense.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If a full data table scan is performed to retrieve low-frequency data, then complete data coverage is achieved, but processing time and computational expense increase significantly

Engineering Contradiction:
Improvedata retrieval completenessVSAvoidquery processing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system pre-computes and stores frequency information for all data records in an index table before queries are executed. This preliminary action allows the query processor to instantly identify low-frequency records without scanning the entire data table, thus achieving complete data coverage while minimizing query processing time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

An index table is introduced as an intermediary structure between the query processor and the main data table. This index table stores pre-computed frequency information and record locations, serving as a mediator that enables fast identification of low-frequency records without requiring direct scanning of the large data table.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If the entire data table is scanned to ensure no low-frequency records are missed, then retrieval completeness is maintained, but resource utilization increases

Engineering Contradiction:
Improveretrieval completenessVSAvoidcomputational resource utilization
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system extracts only the essential frequency information and record location data from the complete data table and stores it in a separate index table. This extraction allows the query processor to retrieve low-frequency records using only the index table, maintaining retrieval completeness while dramatically reducing computational resource utilization during query execution.

Inventive Principle:
Principle #2Taking out (Extraction)

3Speed

If traditional indexing methods are used on large data tables, then query performance improves, but the index structure becomes complex and maintenance overhead increases

Engineering Contradiction:
Improvedata retrieval speedVSAvoidindex structure complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The system changes the indexing parameter from traditional structural indexes (based on data values and relationships) to a frequency-based index that stores only the occurrence count and location information of each record. This parameter change simplifies the index structure while maintaining fast retrieval capability for low-frequency records.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11321392B2Light weight index for querying low-frequency data in a big data environment
Publication Date: 2022.05.03 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11321392B2 patent drawing
  • US11321392B2 patent drawing
  • US11321392B2 patent drawing

AI summary

The present disclosure relates to searching for and committing low-frequency data to a database. An example method generally includes receiving, from a requesting application, a query for data from the data repository. A database system retrieves a set of indices associated with the data specified in the query from an index table in the data repository. Upon determining that the set of indices comprises a non-null set, the database system retrieves records associated with each index in the set of indices from a data table associated with the index table and returns the retrieved records to the requesting application.