Business-Driven Database Archiving via Relationship Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current archiving strategies for database tables are technically driven, failing to identify and prioritize business-critical processes due to the lack of functions that extract relationships between database tables, archiving objects, and business processes, making it complex for customers to manage data volume effectively across heterogeneous system landscapes.
Innovation Solution
A business-driven approach that allows users to select business scenarios and processes to determine related database tables, enabling application teams to create archiving strategies based on business needs, supported by systems administration teams, without requiring real-time data, and utilizing weighting factors for data volume management decisions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If technical monitoring of database tables is performed to determine archiving objects, then database size and growth can be tracked, but business critical processes cannot be identified due to lack of relationship extraction functions
Solution Approach 1:
The patent introduces an intermediary component that extracts and maintains relationships between database tables and business processes. This intermediary layer enables the system to connect technical database monitoring data with business context, allowing archiving decisions to be made based on both database size metrics and business criticality without requiring direct integration between monitoring and business process management systems.
2Productivity
If systems administration teams perform technical analysis of databases to implement archiving strategies, then database management can be maintained, but application teams cannot create business-driven archiving strategies without technical expertise
Solution Approach 1:
The patent enables application teams to perform self-service archiving strategy creation by providing them with direct access to relationship extraction functions and business process data. This allows business users to independently identify archiving candidates based on their domain knowledge without requiring systems administration teams to perform technical analysis, thereby improving ease of operation while maintaining productivity.
3Manufacturing precision
If database table level analysis is performed across heterogeneous system landscapes, then detailed data volume management can be achieved, but system complexity increases due to unique configuration of each system
Solution Approach 1:
The patent implements a universal relationship extraction framework that can operate across heterogeneous system landscapes with unique configurations. The system provides multi-functional capabilities to handle different database types, system configurations, and business process structures through a single unified approach, enabling detailed data volume management precision without proportionally increasing system complexity.
4Quantity of substance
If customers focus on identifying data objects for archiving, then data volume management can be performed, but time is lost that could be used for evaluating residence times and selecting document types
Solution Approach 1:
The patent performs preliminary extraction and maintenance of relationships between database tables and business processes in advance. This preliminary action enables the system to pre-identify archiving candidates and their business context, so when archiving decisions need to be made, the analysis is already complete or near-complete, significantly reducing the time required for evaluating residence times and selecting document types for archiving.
Data Source
AI summary
A computer system maintains a repository of software products. The software products include a plurality of business processes, and each business process includes a business object. The system maintains a plurality of archiving objects, and further maintains a mapping of each business process to at least one business object, a mapping of each business object to at least one related database table, and a mapping of each database table to at least one related archiving object. The system receives a selection of a business process for which data is to be archived, and uses the mapping of the each business process to the at least one business object, the mapping of the each business object to the at least one database table, and the mapping of the each database table to the at least one archiving object to determine the database tables to transmit to the archiving objects.