Schema Stack Management for Zero-Downtime Upgrades

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Managing custom configurations during maintenance operations in enterprise software systems is complex, time-consuming, and requires extended downtime to ensure the custom configuration remains operable post-maintenance.

Innovation Solution

A schema stack management system that enables zero-downtime upgrades by maintaining a first set of synonyms between the cross schema and data spaces for production use, deploying a new cross schema version, and providing connections between extension schemas, allowing for seamless transition between schema versions without disrupting custom configurations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If maintenance operations are performed on the application system, then the application can be upgraded and patched, but the application must be taken offline causing extended downtime and disrupting custom configurations

Engineering Contradiction:

Improveapplication availabilityVSAvoiddowntime duration

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system segments the schema stack into multiple versions (current production schema and new schema) that can operate independently. Synonyms are used to redirect queries to the appropriate schema version, allowing the application to serve requests while maintenance operations are performed on a separate schema instance.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The new schema version is deployed and configured in advance before the maintenance operation begins. Synonyms are pre-configured to point to the new schema, so when the maintenance is complete, the system can seamlessly switch to the new schema without requiring application downtime or reconfiguration.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If the application is taken offline for maintenance, then upgrades and patches can be applied, but custom configurations require additional time and resources to ensure operability after maintenance

Engineering Contradiction:

Improvecustom configuration operabilityVSAvoidmaintenance procedure complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

A copy of the current production schema is created as a new schema version. This copy can be modified during maintenance operations without affecting the running application. The synonym mechanism allows the system to switch between the original and copied schemas, ensuring custom configurations remain intact while enabling safe updates.

Inventive Principle:

Principle #26Copying

3Productivity

If synonyms are maintained between cross schema and data spaces during maintenance, then production use continues without interruption, but the system complexity increases

Engineering Contradiction:

Improveproduction continuityVSAvoidschema management complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

Synonyms act as intermediary objects that bridge the application layer and the underlying schema versions. Instead of modifying application code or data access logic, the synonym mechanism provides a transparent layer that redirects queries to the appropriate schema version, simplifying the management of multiple schema versions while maintaining production continuity.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS12216624B2Schema stack management system for managing extensions through upgrades

Publication Date: 2025.02.04 SAP SE

AI summary

Implementations include a schema stack management system that enables zero-downtime during execution of maintenance procedures on application systems having schema stacks including one or more customer-provided schema extensions.