Database Schema Extraction for Selective Object Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in restoring individual data objects from an unmounted relational database file without reinstalling the database system, which is crucial for managing and accessing electronic documents in enterprise information portals.

Innovation Solution

A method that involves retrieving a previously stored schema corresponding to the data structure of the relational database file, using it to access and reconstruct user-defined tables and records, and then transferring the reconstructed data objects back to a secured RDBMS for restoration, allowing for selective retrieval and addition to the database.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the database system is reinstalled to restore individual data objects from an unmounted database file, then data recovery is possible, but system complexity and time consumption increase significantly

Engineering Contradiction:
Improvedata recovery capabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the database restoration process into two independent parts: the schema (data structure definitions) and the data objects (actual content). By extracting and storing only the schema separately, the system enables selective restoration of individual data objects without requiring the entire database system to be reinstalled. This segmentation allows the restoration process to work with minimal components, reducing system complexity while maintaining data recovery capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary action by extracting and storing the schema (data structure definitions) in advance, before any data loss occurs. This pre-stored schema serves as a template that can be reused during restoration operations. When data objects need to be restored from an unmounted database file, the pre-existing schema eliminates the need to reinstall the entire database system, thereby reducing both time consumption and system complexity while ensuring reliable data recovery.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the entire database system is reinstalled to access individual data objects, then data accessibility is restored, but time consumption increases

Engineering Contradiction:
Improvedata accessibilityVSAvoidrestoration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The schema (data structure definitions) is extracted and stored in advance as a preliminary action. This pre-prepared schema acts as a ready-to-use template that enables immediate restoration of data objects without requiring time-consuming database system reinstallation. When restoration is needed, the system simply applies the pre-stored schema to extract individual data objects from the unmounted database file, dramatically reducing restoration time while ensuring data accessibility.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent extracts only the essential schema (data structure definitions) from the complete database system and stores it separately. This extraction isolates the critical recovery component from the entire database system. During restoration, only this extracted schema is needed to access individual data objects from an unmounted database file, eliminating the time-consuming step of reinstalling the entire database system while maintaining full data accessibility.

Inventive Principle:
Principle #2Taking out (Extraction)

3Productivity

If selective restoration of data objects is implemented without reinstallation, then productivity improves, but technical complexity of the restoration process increases

Engineering Contradiction:
Improverestoration efficiencyVSAvoidrestoration process complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the database into schema (data structure definitions) and data objects (content). This segmentation enables selective restoration by allowing the system to work with only the necessary components. The restoration process becomes more efficient because it operates on segmented, manageable parts rather than requiring complete system reinstallation, thereby improving productivity while keeping the restoration process technically manageable through clear separation of concerns.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

By performing the schema extraction and storage as a preliminary action, the patent prepares the essential recovery template in advance. This preliminary preparation simplifies the actual restoration process, as the system only needs to apply the pre-stored schema to extract specific data objects. The preliminary action reduces the technical complexity of the restoration operation itself while significantly improving productivity by enabling fast, selective data recovery without complete system reinstallation.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7672934B1Method for restoring documents from a database file
Publication Date: 2010.03.02 COHESITY INC
  • US7672934B1 patent drawing
  • US7672934B1 patent drawing
  • US7672934B1 patent drawing

AI summary

Various embodiments of a method and system for accessing an instance of a database file previously created by a secured RDBMS are disclosed. The secured RDBMS is not used to reconstruct tables and records from an unmounted backed up copy of a database file. During backup, a schema file including table and index information is stored along with the database file. During a subsequent restore operation, the schema file may be read for efficiently reconstructing objects from the database file, without having to reload or reinstall the secured RDBMS. For restoring or comparing objects from the backed up database file, a stored procedure in the secured RDBMS may be called.