Data Purging System with Weak Relation Severing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Database systems face inefficiencies due to temporary data being unnecessarily persisted, consuming valuable resources and requiring manual intervention by application developers, which is both inefficient and error-prone.

Innovation Solution

A system for managing data using purging, which includes an input interface for receiving indications of data to be purged, prepared, or restored, utilizing a processor to sever relationships, simulate purging, and restore data using an effective change stack, with a memory to provide instructions for these processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual removal of unneeded data structures is performed by application developers, then data can be removed from the database system, but the process is inefficient and error-prone

Engineering Contradiction:
Improvedata removal efficiencyVSAvoiddata removal accuracy
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The database system automatically identifies and removes unneeded data structures without requiring manual intervention from application developers. The system performs self-diagnosis to detect temporary data that can be purged, eliminating the need for human operators to manually remove data structures.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The manual process of data structure removal by application developers is replaced with an automated electronic system. The database management system uses algorithms and data structure analysis to automatically identify and purge unnecessary data, substituting human mechanical operations with automated computational processes.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If temporary data is persisted in the database system, then data is preserved for potential future use, but valuable system resources are consumed

Engineering Contradiction:
Improvedata preservationVSAvoidsystem resource usage
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system changes the state parameter of data from 'persisted' to 'purged' based on analysis of data structure characteristics and usage patterns. By evaluating whether data structures represent temporary or permanent data, the system dynamically adjusts resource allocation and data retention status to optimize system performance.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The database system selectively discards temporary data structures that are no longer needed while preserving important data. The automated purging mechanism identifies temporary data using unique characteristics of data structures and removes only the appropriate portions, recovering system resources while maintaining data integrity for permanent records.

Inventive Principle:
Principle #34Discarding and recovering

Data Source

PatentUS10572448B1Managing data using purging
Publication Date: 2020.02.25 WORKDAY INC
  • US10572448B1 patent drawing
  • US10572448B1 patent drawing
  • US10572448B1 patent drawing

AI summary

A system for managing data using purging includes an input interface and a processor. The input interface is to receive an indication of a data object to be purged. The processor is to prepare the data object to be purged, which includes severing weak relations of the data object as of a purge prepare time. Preparing the data object to be purged transitions the data object from an operational state to a purge prepared state. The weak relations of the data object are relations to non-purge data objects of an object tree. The data object in a purge prepared state is monitored for access. In response to a detection of an attempt to access the data object, reinstate the data object, which includes rebuilding the weak relations. Reinstating the data object transitions the data object from the purge prepared state to the operational state.