Database Version Upgrade via Shadow Catalog Segmentation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional database upgrade processes require significant resources and cause disruptions, necessitating additional processors and memory to design and interact with new database systems, leading to inefficient use of memory cells and potential service disruptions.

Innovation Solution

The approach involves creating a shadow catalog for the new database version, using a lightweight processor to produce necessary tables, and interacting with existing storage, allowing for a more efficient use of resources and minimizing service disruptions by requiring fewer additional memory cells and enabling near-zero downtime upgrades.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional database upgrade processes are used, then the database can be upgraded to a new version, but significant additional resources (processors and memory) are required and service disruptions occur

Engineering Contradiction:

Improvedatabase version upgrade capabilityVSAvoidadditional memory cells required

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent creates a shadow catalog that is a copy of the system catalog but stored in a separate location (pg_shadow). This shadow catalog allows the new database version to be designed and tested without requiring all resources to be allocated upfront, enabling incremental resource usage during the upgrade process.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The database catalog is segmented into two parts: the original system catalog and the shadow catalog. This segmentation allows the upgrade process to proceed in stages, with the shadow catalog serving as a staging area that doesn't require full resource allocation immediately, thus reducing the quantity of additional memory cells needed at any one time.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If conventional database upgrade processes are used, then the database can be upgraded to a new version, but service disruptions and downtime occur

Engineering Contradiction:

Improvedatabase version upgrade capabilityVSAvoidservice disruption duration

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The shadow catalog is created and prepared in advance before the actual upgrade is executed. This preliminary action allows the new database version structure to be designed and validated without interrupting service, as the shadow catalog exists separately and doesn't interfere with the running database operations.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The shadow catalog acts as an intermediary between the old and new database versions. It serves as a buffer that allows the upgrade process to proceed without direct interference with the running database, minimizing service disruptions by decoupling the upgrade preparation from the active database operations.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If additional processors and memory are provided for database upgrades, then the second version of the database management system can be designed and interacted with, but resource efficiency decreases

Engineering Contradiction:

Improvenew database version development capabilityVSAvoidresource efficiency

Core Design Contradiction:

Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The shadow catalog is created and maintained using the existing database's own resources rather than requiring separate dedicated resources. The system uses its existing memory cells and processing capacity to build and manage the shadow catalog, thereby improving resource efficiency while still enabling new version development.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The existing database resources are made multi-functional by simultaneously supporting both the running database operations and the shadow catalog creation process. This universal usage of resources eliminates the need for dedicated upgrade resources, improving overall resource efficiency while maintaining upgrade capability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS10810248B2Upgrading a database from a first version to a second version

Publication Date: 2020.10.20 SALESFORCE INC

AI summary

A processor can produce a database catalog for a second version of a database management system of the database. The database catalog can store metadata related to definitions of objects or tables included in the second version of the database. A controller can be caused to be established in memory cells being used for the first version of the database. A copy of the database catalog for the second version of the database management system can be stored in the memory cells being used for the first version of the database. The controller, using the copy of the database catalog, can produce the second version of the database management system. The second version of the database management system can be caused to interact with data stored in a storage of the database. The storage can be included in the memory cells being used for the first version of the database.