Master Copy Database Initialization in Hyperscaler Environments

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Traditional methods for initializing a database in a hyperscaler environment are time-consuming, resource-intensive, and prone to errors, and do not scale effectively to support large numbers of customers, making them unsuitable for hyperscaler environments.

Innovation Solution

A system and process that utilize a master copy of application-specific data provided by the customer, which is used to partially initialize a database service within the hyperscaler environment, and then retrieved and expanded upon by a recovery job to complete the initialization, allowing for efficient and secure setup of database services across large scales.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional database initialization methods are used, then database functionality is configured, but the process is time-consuming and resource-intensive

Engineering Contradiction:

Improvedatabase initialization reliabilityVSAvoidinitialization time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-configuring a master copy database with all necessary application-specific content and configuration before deployment. This master copy serves as a template that can be rapidly replicated across multiple customer instances, eliminating the need to perform time-consuming configuration steps during actual database initialization while maintaining full functionality and reliability

Inventive Principle:

Principle #10Preliminary action

2Reliability

If traditional database initialization methods are used, then database setup is completed, but resource consumption is high

Engineering Contradiction:

Improvedatabase setup reliabilityVSAvoidinitialization resource consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent implements copying by creating a pre-configured master copy database that serves as a template. Instead of performing resource-intensive configuration operations for each new database instance, the system replicates the master copy to generate multiple customer-specific databases. This approach dramatically reduces computational resources, processing power, and energy consumption during database initialization while maintaining complete database functionality and setup reliability

Inventive Principle:

Principle #26Copying

3Ease of manufacture

If traditional database initialization methods are used, then database configuration is achieved, but error rate increases

Engineering Contradiction:

Improvedatabase configuration easeVSAvoidinitialization error rate

Core Design Contradiction:

Ease of manufactureVSReliability

Solution Approach 1:

The patent applies preliminary action by performing all configuration steps in advance during master copy creation. The master copy is meticulously configured with all necessary tables, schemas, application-specific content, and database functionalities before being used as a template. This upfront configuration eliminates the need to execute complex configuration sequences during actual database initialization, thereby reducing human error and improving reliability while maintaining ease of setup

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

By replicating the pre-configured master copy to create new database instances, the patent ensures that each customer database receives an exact copy of the validated configuration. This copying approach eliminates errors that could occur during manual or automated configuration processes for each individual instance, as the master copy has already been thoroughly tested and verified

Inventive Principle:

Principle #26Copying

4Productivity

If traditional database initialization methods are used, then database service is provided, but scalability is limited

Engineering Contradiction:

Improvedatabase provisioning speedVSAvoidhyperscaler environment adaptability

Core Design Contradiction:

ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent enables hyperscaler environment adaptability and rapid provisioning by implementing a master copy replication strategy. The pre-configured master copy database serves as a reusable template that can be rapidly replicated to create thousands or millions of customer-specific database instances. This approach allows the system to scale horizontally across the hyperscaler infrastructure, accommodating growing customer demands without proportionally increasing configuration time, resource consumption, or error rates, thereby achieving both high productivity and environment adaptability

Inventive Principle:

Principle #26Copying

Data Source

PatentUS20210349861A1Database setup using a master copy

Publication Date: 2021.11.11 SAP SE

AI summary

A system and method to receive, by a cloud infrastructure database service provider, a request for a new database service from an entity external to the cloud infrastructure, the request including an indication the requested database service is to be created using a master copy of a database service; create, in response to the request, a partially initialized database service and a recovery job to access a resource external to the cloud infrastructure; receive, by the partially initialized database service, a master copy of the requested database service from the external resource, the master copy including data content; and fully initialize the database service using at least some of the data content included in the master copy of the requested database service.