External Database Versioning for Cloud Table Customization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional customization of database tables in cloud-based software applications involves complex processes that consume significant computational resources and storage, particularly for large tables, leading to disruptions in system operations.

Innovation Solution

Customization is performed using an external database that directly writes new database tables with a version identifier, allowing components to read these tables efficiently, eliminating replication and optimizing resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data replication is used for customization in cloud-based systems, then customization capability is achieved, but storage and computational resources are significantly consumed

Engineering Contradiction:
Improvecustomization capabilityVSAvoidstorage resources
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent extracts the customization data storage function from the main cloud-based system by introducing an external database. The external database stores customized database tables separately, eliminating the need for data replication within the cloud system. This extraction resolves the contradiction by maintaining customization capability while significantly reducing internal storage resource consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The external database serves as an intermediary between the cloud-based system and the customization requirements. Instead of replicating data within the cloud system, the external database acts as a mediator that stores customized tables and provides them to the cloud system when needed, reducing internal storage and computational overhead.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If data replication is used for customization in cloud-based systems, then customization capability is achieved, but computational resources are significantly consumed

Engineering Contradiction:
Improvecustomization capabilityVSAvoidcomputational resources
Core Design Contradiction:
Adaptability or versatilityVSPower

Solution Approach 1:

The patent extracts the customization processing from the main cloud-based system by using an external database. The external database handles storage and retrieval of customized tables, eliminating the need for complex data replication processes within the cloud system. This reduces computational resource consumption while maintaining customization capability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The external database acts as an intermediary that handles customization operations externally. Instead of the cloud system performing resource-intensive replication operations, the external database mediates these operations, providing customized data to the cloud system with minimal computational overhead.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If traditional customization processes are used, then customization is achieved, but system operations are disrupted

Engineering Contradiction:
Improvecustomization capabilityVSAvoidsystem operation continuity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the customization storage function from the main cloud-based system by introducing a separate external database. This segmentation allows customization operations to occur independently without disrupting cloud system operations. The external database stores customized tables that can be retrieved when needed without affecting ongoing system processes.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The external database stores customized database tables in advance before they are needed by the cloud system. This preliminary action allows the cloud system to retrieve customized data without disrupting ongoing operations, as the customization data is already prepared and stored externally.

Inventive Principle:
Principle #10Preliminary action

4Adaptability or versatility

If data replication is used for customization, then customization is achieved, but the process is inefficient

Engineering Contradiction:
Improvecustomization capabilityVSAvoidcustomization efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent extracts the customization data storage from the main cloud system to an external database, eliminating the inefficient data replication process. The external database directly stores customized tables without requiring replication through multiple system components, significantly improving customization efficiency and productivity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The external database serves as an efficient intermediary that directly stores and provides customized data to the cloud system. This intermediary approach eliminates the need for complex replication processes, reducing the number of operations required and improving overall customization efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12619592B2External database as source for local system customizing
Publication Date: 2026.05.05 SAP SE
  • US12619592B2 patent drawing
  • US12619592B2 patent drawing
  • US12619592B2 patent drawing

AI summary

A method, a system, and computer program product for customizing settings of cloud-based software applications using an external database as a source are provided. A request to generate a new database table corresponding to a new version of a database table associated with a cloud-based system hosting a cloud-based software application is received. The request is processed to determine a content of the new database table using a data structure of the database table. A version identifier corresponding to the new database table is generated. The version identifier and the new database table are provided, to an external database for storage. A deployment, to a productive system, of the new database table, is controlled for the new database table to be used when executing the cloud-based software application.