Segmented Database Migration for In-Memory Databases

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data migration methods are inadequate for minimizing downtime in large databases, especially in in-memory databases, as they require significant resources and are not easily compatible with all database types, leading to high costs and impracticalities during the migration process.

Innovation Solution

The implementation of segmented data migration, where data is divided into segments based on downtime constraints, allowing for prioritization and parallel or sequential migration, enabling client applications to access completed segments while others are still being migrated, and utilizing a migration system that includes tools for determining segment priorities and managing the migration process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If data migration is performed using traditional mechanisms (creating duplicates at source and target databases), then downtime during migration can be minimized, but the cost increases significantly when databases are storage constrained (e.g., in-memory databases)

Engineering Contradiction:
Improvedowntime during migrationVSAvoidstorage resources
Core Design Contradiction:
Loss of timeVSQuantity of substance

Solution Approach 1:

The patent divides the database table into multiple segments (first segment, second segment, etc.) and migrates them sequentially. This allows the migration process to complete without requiring duplicate storage of the entire table, as each segment is migrated and made available progressively. The segmentation principle resolves the contradiction by reducing the peak storage resource requirement while maintaining continuous availability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a first segment of the table before completing the migration of the second segment. This preliminary action allows client applications to access portions of the data earlier in the migration process, reducing overall downtime without requiring full duplication of the table structure.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If high-speed computing devices are used to minimize downtime during data migration, then migration speed increases, but the mechanism becomes insufficient as database volume increases

Engineering Contradiction:
Improvemigration speedVSAvoidcomputing resources
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

By segmenting the table into multiple smaller units that can be migrated in parallel or sequentially, the patent increases migration productivity without requiring proportional increases in computing resources. Each segment can be processed independently, allowing efficient utilization of available computing resources even as total database volume grows.

Inventive Principle:
Principle #1Segmentation

3Reliability

If duplicate database tables are created during migration, then data availability is maintained, but the cost becomes prohibitive for in-memory databases with limited main memory

Engineering Contradiction:
Improvedata availabilityVSAvoidmain memory
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent migrates the table in segments rather than creating full duplicates. The first segment is made available to client applications before the second segment migration completes, ensuring data availability while using minimal additional main memory. This segmented approach maintains reliability without the prohibitive cost of full duplication in memory-constrained environments.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9927992B2Segmented database migration
Publication Date: 2018.03.27 SAP SE
  • US9927992B2 patent drawing
  • US9927992B2 patent drawing
  • US9927992B2 patent drawing

AI summary

Various examples are directed to systems and methods for database migration. A data migration system may access schema data describing data stored at a database. The data migration system may identify a first segment of the first plurality of records having a first value for a first segmenting parameter and a second segment of the first plurality of records having a second value for the first segmenting parameter. The data migration system may begin to migrate the first segment of the first plurality of records. After the first segment of the first plurality of records is migrated, the data migration system may begin to migrate the second segment of the first plurality of records.