Database Object Archiving System for Memory Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional database systems lack efficient mechanisms for identifying and managing data suitable for archiving, leading to increased Total Cost of Ownership (TCO) and downtime during lifecycle operations, especially in in-memory systems, and fail to comply with data privacy regulations by not efficiently archiving or deleting personal data.
Innovation Solution
A system that efficiently selects object instances for archiving based on predefined criteria, archives them to external storage, supports searching, and handles deletion, reducing memory usage and hardware costs by utilizing a platform that includes a configuration component to specify archiving criteria, an object selection component to identify objects for archiving, and an object archiver to serialize and store the data in a cost-effective cloud storage solution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If data is stored in volatile memory for fast access, then read and write speed is improved, but hardware cost and total cost of ownership increase
Solution Approach 1:
The patent segments data into active data and inactive data, storing active data in volatile memory for fast access and inactive data in external storage for cost efficiency. The archiving system identifies and separates inactive data objects, moving them to external storage while maintaining the ability to retrieve them when needed.
Solution Approach 2:
The patent extracts inactive data objects from the volatile memory database and moves them to external storage. The archiving system identifies data objects that are no longer actively used and extracts them from the main database system, reducing the memory footprint and hardware costs while preserving the data for future retrieval.
2Reliability
If inactive data is retained in the database, then data completeness is maintained, but lifecycle operation time increases
Solution Approach 1:
The patent performs preliminary archiving of inactive data before lifecycle operations are needed. By proactively identifying and archiving inactive data objects in advance, the system prepares the database for faster lifecycle operations without compromising data completeness, as archived data can be quickly retrieved when needed.
Solution Approach 2:
The patent introduces an archiving system as an intermediary between the database and external storage. This intermediary manages the movement of inactive data objects, maintaining data completeness by ensuring archived data can be retrieved, while simultaneously reducing lifecycle operation time by removing inactive data from the active database.
3Productivity
If data archiving mechanisms are added to identify and manage archivable data, then data management efficiency is improved, but system complexity increases
Solution Approach 1:
The patent implements a self-service archiving mechanism where the system automatically identifies inactive data objects and archives them without requiring complex manual intervention. The archiving system uses predefined criteria to autonomously determine which data objects are inactive and should be archived, improving data management efficiency while keeping system complexity manageable through automation.
Data Source
AI summary
Systems and methods to select an object instance from a database storage to archive to an external storage based on an archiving configuration and attribute values of the object instance, transmit the selection to an application associated with the object instance, determine, based on a response received from the application, to archive the object instance, mark the object instance as ready for archiving, identify the object instance as ready for archiving, convert the object instance to an object notation format, transmit the converted object instance to a cloud application for storage in an external storage, in response to a determination that the storage in the external storage is successful, create an index object in the database storage including a subset of fields of the object instance and a link to the converted object instance stored in the external storage, and mark the object instance in the database storage as archived.