Access Schema Layer for Zero Downtime Database Maintenance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing maintenance procedures for applications and databases often result in downtime, which is difficult to minimize, and require significant resources such as computer processing and memory, especially when data copying is involved.

Innovation Solution

Implementing an access schema layer that facilitates exclusive communication between applications and a data schema layer, allowing for zero downtime by using multiple access schemas to manage data communication, including views, triggers, and delta tables to support upgrade and patch procedures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional maintenance procedures are used to upgrade or patch applications and databases, then maintenance operations can be performed, but the application and database must be taken offline resulting in downtime and user unavailability

Engineering Contradiction:
Improveapplication availabilityVSAvoiddowntime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system segments the database access layer into multiple schema instances (first schema, second schema) that can operate independently. This allows different applications to access different schema instances simultaneously, enabling maintenance on one schema while others remain operational, thus eliminating downtime without compromising reliability

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer (schema layer) between the application and the underlying database. This intermediary allows for schema switching and maintains application connectivity during maintenance operations, preventing direct disruption to user access while enabling background maintenance activities

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of manufacture

If data is copied to separate databases during maintenance procedures, then maintenance can be performed, but additional computer processing resources and memory are required

Engineering Contradiction:
Improvemaintenance procedure implementationVSAvoidcomputer processing resources and memory
Core Design Contradiction:
Ease of manufactureVSQuantity of substance

Solution Approach 1:

The patent creates a universal schema layer that serves multiple functions: it enables maintenance operations, provides data isolation, and maintains application connectivity simultaneously. This multi-functional approach eliminates the need for separate copied databases, reducing resource requirements while maintaining ease of maintenance implementation

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

Solution Approach 2:

Instead of physically copying data to separate databases, the patent creates virtual copies through schema abstractions. The schema layer provides a logical representation that can be maintained independently without duplicating the actual data, significantly reducing memory and processing resource requirements while maintaining the ability to perform maintenance operations

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10303665B2Zero downtime maintenance for applications and databases
Publication Date: 2019.05.28 SAP SE
  • US10303665B2 patent drawing
  • US10303665B2 patent drawing
  • US10303665B2 patent drawing

AI summary

Methods, systems, and computer-readable storage media for minimizing downtime during maintenance procedures to an application. In some implementations, actions include executing a first application, executing a second application, and providing an access schema layer that facilitates communication between applications and a data schema layer, the data schema layer including one or more tables of a database, wherein, during a maintenance procedure, the access schema layer includes: a first access schema, the first access schema facilitating exclusive communication between the first application and at least one table of the data schema layer, and a second access schema, the second access schema facilitating exclusive communication between the second application and one or more tables of the data schema layer.