Dynamic Space Allocation for Variable Length Database Fields

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database management systems face inefficiencies in allocating space for fixed length parts of variable length fields, such as VARCHAR fields, leading to wasted storage space and increased access time due to the static nature of space allocation.

Innovation Solution

An enhanced space allocation mechanism dynamically allocates space for the fixed length part of variable length fields based on historical data, using a historical record to estimate the optimal fixed portion length, thereby optimizing storage space and access speed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If static space allocation is used for fixed length part of VARCHAR field, then storage space is simplified to manage, but storage waste increases and access time increases

Engineering Contradiction:
Improvespace allocation management complexityVSAvoidstorage space waste
Core Design Contradiction:
Device complexityVSLoss of substance

Solution Approach 1:

The patent applies dynamics by transitioning from static space allocation to dynamic space allocation for the fixed length part of VARCHAR fields. The system now adjusts the fixed length portion size based on actual data characteristics and access patterns, allowing the allocation to adapt and change over time rather than remaining fixed, thereby reducing storage waste while maintaining manageable complexity through automated management.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the parameter of fixed length portion size from a static value to a dynamic value that can be adjusted based on data characteristics. By monitoring actual data insertion patterns and modifying the fixed length allocation parameter accordingly, the system optimizes storage utilization without significantly increasing management complexity, as the changes are driven by automated analysis of data patterns.

Inventive Principle:
Principle #35Parameter changes

2Device complexity

If static space allocation is used for fixed length part of VARCHAR field, then storage space is simplified to manage, but data access speed decreases

Engineering Contradiction:
Improvespace allocation management complexityVSAvoiddata access speed
Core Design Contradiction:
Device complexityVSSpeed

Solution Approach 1:

The system dynamically adjusts the fixed length portion size based on actual data access patterns and characteristics. By making the allocation adaptive rather than static, the system can optimize for frequently accessed data patterns, improving access speed while the automated management keeps complexity manageable.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent implements feedback mechanisms that monitor data insertion patterns and access characteristics, then use this information to adjust the fixed length portion allocation. This feedback loop allows the system to learn from actual usage and optimize performance automatically, improving access speed without requiring manual intervention or complex management overhead.

Inventive Principle:
Principle #23Feedback

3Loss of substance

If dynamic space allocation is used for fixed length part of VARCHAR field, then storage waste is reduced and access speed improves, but system complexity increases

Engineering Contradiction:
Improvestorage space wasteVSAvoidspace allocation mechanism complexity
Core Design Contradiction:
Loss of substanceVSDevice complexity

Solution Approach 1:

The system performs self-service by automatically analyzing its own data patterns and adjusting space allocation without external intervention. The database management system monitors its own VARCHAR field usage and autonomously optimizes the fixed length portion size, reducing storage waste while keeping the complexity contained within the automated self-management process rather than requiring complex external control mechanisms.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent uses feedback from actual data usage patterns to automatically adjust allocation parameters. The system monitors data insertion and access patterns, then uses this feedback to dynamically optimize the fixed length portion size, achieving reduced storage waste while managing complexity through automated closed-loop control rather than manual configuration.

Inventive Principle:
Principle #23Feedback

4Speed

If dynamic space allocation is used for fixed length part of VARCHAR field, then data access speed is improved, but system complexity increases

Engineering Contradiction:
Improvedata access speedVSAvoidspace allocation mechanism complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The system uses feedback from data access patterns to automatically adjust the fixed length portion allocation. By monitoring which data is accessed most frequently and how it is structured, the system dynamically optimizes allocation to improve access speed while the automated nature of the adjustment keeps complexity manageable within the database management system.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The database management system performs self-optimization by automatically analyzing its own data access patterns and adjusting space allocation accordingly. This self-service approach improves data access speed through adaptive allocation while containing complexity within the automated management framework, eliminating the need for manual configuration or complex external control systems.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7720874B2Dynamically allocating space for a fixed length part of a variable length field in a database table
Publication Date: 2010.05.18 X CORP
  • US7720874B2 patent drawing
  • US7720874B2 patent drawing
  • US7720874B2 patent drawing

AI summary

An enhanced space allocation mechanism (ESAM) for dynamically allocating space for a fixed length part of variable length fields, such as VARCHAR fields, in database tables. Each record in such a variable length field has a fixed length part, a variable length part, and a pointer to the variable length part. The ESAM determines how much space to allocate based on the data that was historically put into these tables. In one embodiment, a database management system (DBMS) maintains a historical record that includes fields identifying the table, column and application ID, as well as fields that track a count and a total length. For each variable length field in a Structured Query Language (SQL) statement such as CREATE table or ALTER table, the DBMS finds a matching historical record, determines an estimated optimal fixed portion length based on the matching historical record, and sets a space allocation length for the fixed length part of the variable length field based on the estimated optimal fixed portion length. This dynamic space allocation approach is especially advantageous in situations where an empty table will be loaded with a massive amount of data.