Recursive Object Reference Structures for Complete Data Purging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Identifying the correct and exhaustive scope of data objects for purging in large or complex databases is challenging, leading to errors and inconsistencies, such as orphaned data records, which can hinder storage space optimization and compliance with data regulations.
Innovation Solution
An object reference structure is generated through recursive queries and automatic analysis of data object attributes to identify and visualize relationships between data objects, facilitating accurate data purging by presenting a graphical representation of these relationships.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual identification of data objects for purging is performed in large or complex databases, then the purging process can be executed, but errors and inconsistencies such as orphaned data records occur due to incomplete identification of relevant data objects
Solution Approach 1:
The patent introduces an object reference structure as an intermediary data structure that mediates between the database schema and the purging process. This structure automatically captures reference relationships between data objects, serving as a mediator that eliminates the need for complex manual identification while ensuring complete and accurate identification of all related data objects for purging.
Solution Approach 2:
The patent performs preliminary action by automatically generating the object reference structure before the purging process begins. This pre-computed structure contains all reference relationships, enabling the purging system to quickly and accurately identify all relevant data objects without performing complex analysis during the actual purging operation.
2Reliability
If comprehensive identification of all related data objects is performed to avoid orphaned records, then data consistency is improved, but the time and computational resources required for the purging process increase
Solution Approach 1:
The object reference structure is built in advance before purging operations are needed. By performing the comprehensive analysis of reference relationships preliminarily and storing results in the object reference structure, the system achieves both complete identification of related data objects and fast execution during actual purging operations.
Solution Approach 2:
The patent creates a copy of the reference relationship information in the object reference structure, which mirrors the database schema's reference relationships. This copy enables quick querying and identification of all related data objects without needing to traverse the actual database relationships during purging operations.
3Productivity
If the purging process targets only directly specified data objects, then the process is simple and fast, but related data objects are missed leading to orphaned records and database inconsistencies
Solution Approach 1:
The object reference structure serves as an intermediary that pre-computes and stores all reference relationships. During purging, the system queries this structure to quickly identify all related data objects (direct and indirect) without performing complex traversals, thus maintaining both speed and completeness.
Solution Approach 2:
The patent segments the complex task of identifying all related data objects into a separate preprocessing step that builds the object reference structure. This segmentation allows the purging process itself to simply query the pre-built structure, maintaining simplicity and speed while ensuring completeness through the comprehensive nature of the pre-computed relationships.
Data Source
AI summary
Systems and methods described herein relate to the automated generation of object reference structures for data purging processes. A primary query is executed in a database to identify first data objects with reference relationships to a root data object. Secondary queries are executed in the database to identify additional data objects with reference relationships to the first data objects or to other additional data objects identified in a previous one of the secondary queries. An object reference structure is generated based on the reference relationships among the root data object, the first data objects, and the additional data objects. The graphical representation is presented via a user interface. A purge instruction can be received with respect to at least part of the object reference structure. Execution of a data purge is triggered to purge data from the database according to the purge instruction.