Virtual Database Table Deployment for Data Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In enterprise software applications, particularly those hosted on cloud platforms, redundant data across multiple database instances leads to inefficient resource usage, especially in memory-intensive systems, as the same data is duplicated across different instances, wasting resources and requiring costly infrastructure to manage.

Innovation Solution

Deploying a virtual table linked to a master database table, with triggers to detect changes and decouple the virtual table when actual data updates are needed, allowing the virtual table to reference the master data without duplication, thus optimizing resource usage by eliminating redundant data storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the same data is duplicated across multiple database instances, then data availability and access independence are improved, but memory resource usage and infrastructure costs increase

Engineering Contradiction:
Improvedata availabilityVSAvoidmemory resource usage
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent merges data storage across multiple database instances by implementing a sharing mechanism where the same physical data storage location is referenced by multiple database instances. This allows data to be shared rather than duplicated, reducing memory resource usage while maintaining data availability through the sharing interface.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal data storage location that serves multiple database instances simultaneously. The shared data storage location functions as a universal resource that can be accessed by any number of database instances, eliminating the need for separate copies of the same data in each instance.

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

2Quantity of substance

If data is shared across multiple database instances, then memory resource usage is reduced, but data integrity and update consistency become more difficult to maintain

Engineering Contradiction:
Improvememory resource usageVSAvoiddata integrity
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent implements a feedback mechanism through deployment triggers that monitor and detect changes to shared data. When data is modified in one database instance, the trigger detects the change and initiates appropriate actions to maintain consistency, such as notifying other instances or updating references, thereby preserving data integrity through continuous monitoring and response.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent employs preliminary actions by locking shared data before modifications are made. This prevents concurrent modifications that could lead to inconsistency, ensuring that only one instance can modify the data at a time. The lock mechanism prepares the system in advance to maintain data integrity by controlling access before the actual modification occurs.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11853286B2Dynamic deployment of multiple database systems with data reduction
Publication Date: 2023.12.26 SAP SE
  • US11853286B2 patent drawing
  • US11853286B2 patent drawing
  • US11853286B2 patent drawing

AI summary

In some implementations, there is provided a method that includes detecting a first database table at a first database instance and a second database table at a second database instance, the first database table and the second database table both including a set of data, the set of data being a same data for both the first database table and the second database table; in response to the detecting, deploying the second database table, such that the second database table comprises a virtual table linked to the set of data of the first database table; and deploying a first trigger and/or a second trigger to detect whether a request is received to perform a change to the set of data at the first database table at the first database instance and/or the second database table at the second database instance. Related systems, methods, and articles of manufacture are also disclosed.