Database Upgrade via Separate Read Write Channels

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database upgrade processes often require downtime, as they necessitate creating backups and running upgrades in parallel to production systems, which can result in minimal but still significant downtime and increased memory consumption.

Innovation Solution

The implementation of a multi-database-schema approach using separate read and write channels allows for concurrent access to database tables between different versions of a database application, enabling bi-directional data transformation and synchronization, thereby minimizing downtime and memory usage during upgrades.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If upgrades run in parallel to production system with clones of tables and data replication, then upgrade can be performed with minimal downtime, but memory consumption increases significantly

Engineering Contradiction:
ImprovedowntimeVSAvoidmemory consumption
Core Design Contradiction:
Loss of timeVSQuantity of substance

Solution Approach 1:

The patent segments the database access into separate read channels and write channels. The read channel accesses the production database while the write channel accesses the upgraded database, allowing parallel operation without duplicating entire table structures in memory simultaneously. This segmentation enables minimal downtime upgrades while controlling memory consumption by avoiding full data duplication.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer (access schemas and channel management) between the application and the database tables. This intermediary enables seamless switching between read and write operations across different database versions without requiring complete data cloning, thus reducing memory overhead while maintaining continuous availability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If separate read and write channels are implemented with bi-directional synchronization, then concurrent access to multiple database versions is enabled, but system complexity increases

Engineering Contradiction:
Improveconcurrent access capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements universal access schemas that can handle both read and write operations across multiple database versions through a unified interface. The channel management system provides multi-functional capabilities by routing read operations to the production database and write operations to the upgraded database, enabling concurrent access without proportionally increasing system complexity.

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

3Productivity

If data is duplicated for both old and new software during upgrade, then parallel deployment is enabled, but additional memory consumption occurs

Engineering Contradiction:
Improveparallel deployment capabilityVSAvoidmemory consumption
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The patent implements dynamic channel switching that allows the system to adaptively route read and write operations to appropriate database versions based on operational needs. This dynamic approach enables parallel deployment of old and new software while avoiding static data duplication, as the system selectively accesses data from either the production or upgraded database depending on the operation type, thereby controlling memory consumption.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9910665B2Simultaneous operation of multiple versions of an application using bidirectional synchronization and separated read write channels
Publication Date: 2018.03.06 SAP SE
  • US9910665B2 patent drawing
  • US9910665B2 patent drawing
  • US9910665B2 patent drawing

AI summary

An upgrade of a first version of a database application to a second version of a database application that both have a same data schema is initiated. The first database application has a first access schema such that at least one table in the data schema is linked to the first access schema. The second version of the database application has a second access schema such that at least one table in the data schema is linked to the second access schema. The first access schema differs from the second access schema. Subsequently, concurrent access is provided for each access schema to at least one database table in the data schema to both the first version of the database application and the second version of the database application. The concurrent access is enabled by using separate read and write channels. Related apparatus, systems, techniques and articles are also described.