Relational Database Conversion for Cloud Archiving

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Relational databases in medical and pharmacy fields face challenges in efficiently backing up and purging historical data, as transferring large amounts of data to a cloud-based environment is time-consuming and prone to interruptions, requiring additional physical disc space and causing delays.

Innovation Solution

A system and method for converting relational database files on a client server into operational database files using the FTP protocol, which are then transferred to a remote archival server in a cloud-computing environment, allowing for efficient purging and archiving while maintaining the same reporting capabilities for both active and archived files.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If relational database files are transferred line by line to a remote server, then the data can be archived in a cloud-computing environment, but the transfer process becomes extremely time-consuming and requires overnight operation

Engineering Contradiction:
Improvedata archiving completionVSAvoidtransfer time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent divides the relational database into separate data files that can be independently identified and transferred. Instead of transferring the entire database line by line through complex queries, the system segments the data into discrete files that can be bulk-transferred, significantly reducing transfer time while ensuring complete archiving of all database contents.

Inventive Principle:
Principle #1Segmentation

2Quantity of substance

If physical disc space is added to the client server to maintain backup files, then historical data can be stored locally, but the cost and time required for maintenance increase

Engineering Contradiction:
Improvestorage capacityVSAvoidmaintenance complexity
Core Design Contradiction:
Quantity of substanceVSEase of manufacture

Solution Approach 1:

The patent extracts historical data files from the active relational database on the client server and transfers them to a remote archival server. This removal of historical files from the local system frees up physical disc space on the client server, reducing the need for additional hardware while maintaining accessibility to archived data through the remote server.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If network transfer is interrupted, then the transfer process must start over from the beginning, but this causes additional delays and reduces efficiency

Engineering Contradiction:
Improvetransfer integrityVSAvoidtransfer efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements a file transfer mechanism that establishes the complete file structure and begins transferring files in sequence. The system is designed to handle interruptions by maintaining knowledge of the transfer state, allowing resumption without complete restart. Files are transferred with their complete path information, enabling the system to track progress and resume efficiently after network interruptions.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11422972B2Relational database conversion and purge
Publication Date: 2022.08.23 CERNER INNOVATION INC
  • US11422972B2 patent drawing
  • US11422972B2 patent drawing
  • US11422972B2 patent drawing

AI summary

A computer implemented method, system and media are provided to convert relational database files hosted on a client server to operating database files. The operating database files are transferred using FTP protocol to a remote archival server. A relational database is created from the transferred operating database files on the remote archival server.