Numeric Field Compression via Dynamic Storage Sizing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database management systems inadequately compress numeric, decimal, and date fields, leading to inefficient storage and retrieval of data, as they often use fixed storage sizes regardless of actual data values, resulting in suboptimal performance and increased storage costs.

Innovation Solution

Implementing a method that uses fixed-length compressed fields for decimal, numeric, and date data, where the size is determined by the range of values, allowing data within specified ranges to be stored in a compressed format and outside ranges in an uncompressed format, eliminating the need for a length value and optimizing storage based on actual data distributions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If fixed-length storage is used for decimal, numeric, and date fields, then data retrieval speed is improved, but storage space is wasted

Engineering Contradiction:
Improvedata retrieval speedVSAvoidstorage space
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The patent applies dynamics by transitioning from static fixed-length storage to dynamic variable-length storage. The system automatically adjusts the storage length of decimal, numeric, and date fields based on the actual data content, allowing the storage structure to adapt dynamically to different data scenarios, thus resolving the contradiction between retrieval speed and storage efficiency

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the storage parameter from fixed length to variable length. By modifying the storage mechanism to use variable-length fields with appropriate length indicators, the system optimizes both retrieval performance (maintaining direct access capability) and storage utilization (reducing wasted space), effectively resolving the technical contradiction

Inventive Principle:
Principle #35Parameter changes

2Quantity of substance

If variable-length storage is used for decimal, numeric, and date fields, then storage space is saved, but data retrieval complexity increases

Engineering Contradiction:
Improvestorage spaceVSAvoiddata retrieval complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-structuring variable-length fields with embedded length indicators or delimiters. This preliminary organization of data with metadata about field lengths allows the retrieval mechanism to efficiently navigate and extract data without complex parsing, thus saving storage space while maintaining retrieval simplicity

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary element (such as length prefixes, separators, or metadata structures) that mediates between the variable-length data and the retrieval mechanism. This intermediary provides structural information that simplifies the retrieval process, allowing the system to benefit from variable-length storage without significantly increasing retrieval complexity

Inventive Principle:
Principle #24Intermediary (Mediator)

3Quantity of substance

If compression is applied to all data fields, then storage cost is reduced, but processing performance deteriorates

Engineering Contradiction:
Improvestorage costVSAvoidprocessing performance
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The patent applies local quality by implementing selective compression strategies where different compression techniques or levels are applied to different data fields or different ranges of values within fields. This localized approach optimizes storage cost for specific data patterns while minimizing the impact on processing performance for frequently accessed or critical data

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent applies partial action by implementing compression only for data that benefits from it, rather than universally compressing all fields. The system identifies and applies compression selectively based on data characteristics, access patterns, and storage requirements, thus reducing storage cost while avoiding the performance penalty of compressing all data

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS8495034B2Numeric, decimal and date field compression
Publication Date: 2013.07.23 TERADATA US INC
  • US8495034B2 patent drawing
  • US8495034B2 patent drawing
  • US8495034B2 patent drawing

AI summary

A method, apparatus, and article of manufacture for accessing data in a computer system. Compression and decompression functions are associated with a column of the table, in order to perform compression of decimal, numeric or date data stored in the column when the data is inserted or updated in the table, and in order to perform decompression of the data stored in the column when the data is retrieved from the table. The compression function compresses and stores the data in a fixed-length compressed field in the column without a length value, and the fixed-length compressed field has a size that is determined by a range of values for the data stored in the fixed-length compressed field. The decompression function retrieves and decompresses the data from the fixed-length compressed field.