Database Archive Control Table for Selective Data Modification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data archiving systems are read-only, making it inefficient and error-prone to alter archived data, as users tend to keep unarchived data to allow changes, leading to delayed archiving and database performance issues.

Innovation Solution

A database system with a control table containing change rule information for archived data documents, allowing specific data fields to be altered while keeping the original document intact, with changes stored separately in a log table for history and security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data is archived in a read-only archive system, then data storage efficiency is improved and database size is reduced, but the ability to alter archived data is lost

Engineering Contradiction:
Improvedata archiving efficiencyVSAvoiddata alterability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The system segments data into immutable archived portions and mutable changeable portions. The control table separates change rule information from archived data, allowing specific data fields to be marked as alterable while maintaining the read-only nature of the archive system itself. This enables selective modification of archived data without compromising the integrity of the archive structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The control table acts as an intermediary between the read-only archive system and the need for data modification. It stores change rule information that mediates between the archived data and user modification requests, enabling the system to determine which archived data can be altered and how, without requiring direct write access to the archive system.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If archived data is reloaded into the database for modification, then data alterability is improved, but administrative effort and time consumption increase significantly

Engineering Contradiction:
Improvedata alterabilityVSAvoidadministrative time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by pre-storing change rule information in the control table alongside archived data. This allows the system to determine alterability and process modifications directly on archived data without requiring preliminary reloading operations. The change rules are prepared in advance, enabling efficient in-place modifications.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If archived data is reloaded, modified and re-archived repeatedly, then data alterability is maintained, but error potential and operational complexity increase

Engineering Contradiction:
Improvedata alterabilityVSAvoiderror resistance
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

Instead of the conventional approach of reloading data to modify it, the system inverts the process by enabling direct modification of archived data through change rules stored in the control table. This reversal eliminates the need for repeated reload-modify-rearchive cycles, reducing error potential while maintaining data alterability.

Inventive Principle:
Principle #13The other way round (Inversion)

4Adaptability or versatility

If unarchived data is kept in the database to allow changes, then data alterability is improved, but database performance and size management deteriorate

Engineering Contradiction:
Improvedata alterabilityVSAvoidsystem performance
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system applies local quality by enabling alterability only for specific data fields marked in the control table, rather than keeping all data unarchived. This allows the database to maintain optimal performance with archived data while still permitting necessary modifications to specific fields through the change rule mechanism, eliminating the need to retain entire records in the active database.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS7953712B2Computer system, a database for storing electronic data and a method to operate a database system
Publication Date: 2011.05.31 SAP SE
  • US7953712B2 patent drawing
  • US7953712B2 patent drawing
  • US7953712B2 patent drawing

AI summary

A computer system includes a database containing a plurality of data documents stored thereon, each data document containing at least one data field, and an archive system for electronically archiving data documents originating from the database. The database includes a control table stored thereon containing change rule information pertaining to the at least one data field of a data document archived in the archive system.