Database Content Migration Queues for Cache and Resource Efficiency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database migration technologies are inefficient and lack flexibility, leading to resource wastage and inaccurate migration processes, especially when moving large volumes of data from on-premises to cloud-based databases.

Innovation Solution

A database migration management tool that provides fine-grained management and a dynamically customizable interface, utilizing an optimal migration cache size, prioritization based on entry dates and sizes, queuing, and continuous monitoring to enhance efficiency and accuracy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If conventional database migration technology is used, then migration can be performed, but efficiency and accuracy are poor leading to resource wastage

Engineering Contradiction:
Improvemigration efficiencyVSAvoidresource consumption
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent segments the database migration process into multiple queues (initial queue and next queue) with fine-grained control over individual database record entries. Each entry is independently prioritized and migrated based on specific criteria, allowing efficient resource utilization while maintaining high migration throughput

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically changes migration parameters including cache size optimization (determining optimal migration cache size), prioritization criteria (based on entry dates and sizes), and queue management strategies to maximize migration efficiency while minimizing resource consumption

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If conventional database migration technology is used, then migration can be performed, but flexibility and customization are limited

Engineering Contradiction:
Improvemigration flexibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a dynamically customizable interface that allows users to adjust migration parameters, prioritization criteria, and queue configurations in real-time. The system adapts to different migration scenarios by changing its behavior based on user inputs and system conditions, providing high flexibility without requiring complex custom development

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The migration management tool serves multiple functions including queue management, prioritization, cache optimization, progress monitoring, and error handling within a single unified system. This multi-functional approach provides comprehensive flexibility while maintaining manageable system complexity through integration

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

3Measurement precision

If conventional database migration technology is used, then migration can be performed, but accuracy and monitoring are insufficient

Engineering Contradiction:
Improvemigration accuracyVSAvoidmonitoring capability
Core Design Contradiction:
Measurement precisionVSExtent of automation

Solution Approach 1:

The system continuously monitors migration progress with fine-grained tracking of individual database record entries. Real-time feedback on migration status, performance metrics, and error conditions enables accurate measurement of migration accuracy and automated adjustment of migration strategies to maintain high precision

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20250217331A1Method and system for migrating database content onto new database infrastructure
Publication Date: 2025.07.03 JPMORGAN CHASE BANK NA
  • US20250217331A1 patent drawing
  • US20250217331A1 patent drawing
  • US20250217331A1 patent drawing

AI summary

A system configured to: determine an optimal migration cache size; interface with a source database; index each respective entry from among the plurality of database record entries based on their respective database record entry dates; respectively prioritize each entry from among the plurality of database record entries for migration based on their plurality of respective database record entry dates and sizes; queue a queue of unmigrated database record entries for migration based on each respective prioritization; and initiate a migration of each respective entry from among the queue of unmigrated database record entries.