Migration to an In-Memory Database with Uptime Pre-Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Migrating from a non-in-memory database to an in-memory database results in significant downtime, which is detrimental to user satisfaction, especially for mission-critical enterprise applications.
Innovation Solution
A specialized software update manager (SUM) with a database migration option (DMO) that allows for pre-migration of a substantial portion of the non-in-memory database during uptime, using a landscape transformation replication server and trigger-based replication to create a shadow system, reducing the data load during the downtime phase.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If database migration is performed using traditional two-step approach (uptime phase and downtime phase), then migration can be completed, but downtime is significant and user access is interrupted
Solution Approach 1:
The patent applies preliminary action by migrating a substantial portion of the database during the uptime phase before the downtime phase begins. The system identifies and migrates tables and structures that can be transferred in advance, so that when the downtime phase starts, only a smaller portion of the database needs to be migrated, significantly reducing the overall downtime and maintaining user access continuity.
Solution Approach 2:
The patent segments the database migration process into distinct phases: an uptime phase where tables and structures are migrated before downtime, and a downtime phase where remaining tables are migrated. This segmentation allows the system to perform migration activities during operational hours for critical data, then complete the migration during scheduled downtime with minimal impact on user access.
2Ease of operation
If entire database is migrated during downtime phase, then migration is simple to implement, but user access is completely interrupted
Solution Approach 1:
The system performs preliminary migration actions during the uptime phase by identifying and transferring substantial portions of the database (tables, structures, functions, triggers) before the downtime phase. This preliminary action reduces the scope of work required during downtime, allowing the migration to be completed faster and with less interruption to user access, while still maintaining implementation simplicity through automated identification and migration processes.
3Device complexity
If no tables are migrated during uptime phase, then migration process is simple, but downtime is maximized
Solution Approach 1:
The patent implements preliminary action by automatically identifying and migrating tables and structures during the uptime phase before downtime begins. The system determines which tables can be migrated in advance and executes the migration, significantly reducing the amount of work required during the downtime phase and minimizing overall downtime while managing process complexity through automated decision-making.
Solution Approach 2:
The system employs feedback mechanisms to monitor database structures, identify migratable tables, and determine the optimal migration strategy during the uptime phase. This feedback loop allows the system to dynamically decide which tables to migrate in advance based on current database state, ensuring complex migrations are managed systematically while maximizing downtime reduction.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
In an example embodiment, a solution is provided that selects a portion of a non-in-memory database to migrate prior to a database migration option (DMO) performing a downtime portion of the migration. While it is typically not possible for the entire database to be migrated prior to the downtime portion due to the need for certain portions of the database to be used for the DMO portion itself, a substantial portion of the non-in-memory database can be migrated prior to the DMO performing the downtime portion of the migration by using specialized techniques. By migrating a substantial portion of the database prior to the downtime portion, the size of the portion of the database that needs to be migrated during the downtime portion is reduced, thus substantially reducing the length of time needed for the downtime portion.