Database Partition Management via Virtual Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

High database update frequency leads to increased history data in current partitions, resulting in degraded query performance and resource-intensive lazy move operations, which are typically performed during non-peak hours to minimize system impact.

Innovation Solution

Implement virtual partitioning by mapping physical partitions to logical partitions, allowing lazy move operations to occur without physical data movement, thereby reducing I/O costs and maintaining system efficiency by controlling data dirtiness through appropriate partitioning intervals.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If periodic lazy move operations are performed to transition older database rows from current partition to history partition, then data management efficiency is improved, but system resources are consumed and query response time is slowed down

Engineering Contradiction:
Improvedata management efficiencyVSAvoidquery response time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent segments the database table into multiple partitions based on transaction time, with each partition containing data for a specific time range. This segmentation allows the system to manage different time periods independently, enabling efficient lazy move operations that transition entire partitions rather than individual rows, thereby improving data management efficiency while minimizing impact on query performance through parallel processing capabilities

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary action by pre-defining partition schemas and establishing partitioning rules in advance. The system proactively manages partition transitions before they become critical, scheduling lazy move operations during off-peak periods based on predetermined criteria. This preliminary organization and planning reduces the computational burden during actual data transitions and minimizes disruption to query operations

Inventive Principle:
Principle #10Preliminary action

2Stability of the object's composition

If physical data movement is performed to transition older database rows from current partition to history partition, then data organization is improved, but I/O resource cost increases

Engineering Contradiction:
Improvedata organizationVSAvoidI/O resource cost
Core Design Contradiction:
Stability of the object's compositionVSLoss of energy

Solution Approach 1:

The patent employs copying mechanisms where partition metadata and transaction time range definitions are replicated and managed centrally. When lazy move operations are performed, the system copies partition definitions and updates mappings rather than physically moving every data row. This approach maintains proper data organization through updated references while dramatically reducing I/O resource consumption by avoiding redundant physical data transfers

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent introduces a logical partitioning dimension that operates independently from physical storage locations. Data can be organized into multiple logical partitions simultaneously, with each partition representing a different time range or classification. This logical dimension allows the system to manage data organization through virtual partitioning and mapping, reducing the need for physical data movement while maintaining organized data structures

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

Data Source

PatentUS9158802B2Database partition management
Publication Date: 2015.10.13 TERADATA US INC
  • US9158802B2 patent drawing
  • US9158802B2 patent drawing
  • US9158802B2 patent drawing

AI summary

Apparatus, systems, and methods may operate to receive a request to move at least a portion of a database table stored on a tangible medium from a current partition to a history partition, wherein the database table is partitioned into physical partitions according to a selected mapping update frequency. In response to receiving the request, activities may include modifying a logical partitioning of the database table by updating a mapping of the physical partitions to logical partitions. Other apparatus, systems, and methods are disclosed.