Database Archiving Table Integration for Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing archiving systems face synchronization issues and require additional resources due to separate backup and archiving systems, leading to increased maintenance and costs.

Innovation Solution

Integrating archiving into existing data management systems by adding an archiving table in the database, using a binary large object field to store archived data, and utilizing a combination of high-throughput and non-volatile memory to store current and archived data respectively, allowing for seamless backup and access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If archiving is implemented using a separate independent system with dedicated storage medium, then data preservation and compliance requirements are met, but synchronization problems occur between different storage media and additional resources are required for setup, operation, and maintenance

Engineering Contradiction:
Improvedata preservationVSAvoidsystem integration
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the archiving function with the existing database system by integrating archiving tables directly into the database structure. This consolidation eliminates the need for separate archiving systems and their dedicated storage media, while maintaining data preservation capabilities through unified backup procedures that backup both current and archived data together.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The existing database system is enhanced to perform multiple functions: storing current organizational data, storing archived data copies, and managing both active and archived records within a single unified system. This multi-functionality eliminates the need for separate specialized archiving infrastructure.

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

2Reliability

If separate backup systems are implemented for both archiving and backing up archives, then data security is enhanced, but maintenance resources and operational complexity increase

Engineering Contradiction:
Improvedata securityVSAvoidmaintenance resources
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent consolidates backup operations into a single unified backup system that backs up the entire database including both current data and archived data stored in archiving tables. This eliminates the need for separate backup systems for archiving and archive backup, reducing maintenance resources while maintaining comprehensive data security.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If archiving and backing up occur at different rates and overlap, then data retention requirements are met, but synchronization issues cause backed up data to vary from archived data

Engineering Contradiction:
Improvedata retentionVSAvoiddata synchronization
Core Design Contradiction:
ReliabilityVSMeasurement precision

Solution Approach 1:

By storing archived data in archiving tables within the same database system, the patent enables unified backup operations that capture both current and archived data in a single consistent backup. This eliminates synchronization issues between separate archiving and backup systems, ensuring backed up data matches archived data while maintaining data retention requirements.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS9639538B2Embedding archived data in a data source
Publication Date: 2017.05.02 SAP SE
  • US9639538B2 patent drawing
  • US9639538B2 patent drawing
  • US9639538B2 patent drawing

AI summary

Archiving may be integrated into an organization's existing data management systems instead of being configured as a separate system. This integration may occur by adding an archiving table to an existing database of the organization containing data that is to be archived. The archiving table may include multiple records, each record storing a binary large object representing a complete, self-contained archive of the organization's data at a preselected time. Incorporating archiving and archived data into the organization's existing data management systems in this manner may eliminate the need for a dedicated archiving system and may eliminate synchronization and interconnectivity issues with an independent archiving system.