Directory Service Log Fields for Schema Change Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In directory service environments, managing changes to database schema and data is complex due to shared usage among applications, leading to unneeded objects and increased storage demands, with limited ability to determine usage and data relationships, resulting in degraded performance.
Innovation Solution
A method is introduced to track system changes by adding log fields to a directory service database, monitoring application identity and data access, logging usage history, and analyzing relationships to determine maintenance actions, allowing for controlled deployment and rollback of changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If database schema and data are shared among multiple applications without tracking, then system complexity is reduced and ease of operation is improved, but data integrity deteriorates and loss of information increases due to untracked changes
Solution Approach 1:
The patent applies preliminary action by pre-defining log fields in the database schema before changes occur. These log fields are prepared to capture application identity, change type, and timestamp information, enabling automatic tracking of all modifications to shared data without requiring complex real-time analysis when changes happen.
Solution Approach 2:
The patent implements feedback by continuously monitoring and logging changes to database schema and data, then analyzing this logged information to identify unused objects and generate maintenance recommendations. This feedback loop enables the system to adapt to changes while maintaining data integrity awareness across multiple applications.
2Measurement precision
If comprehensive logging of all changes is implemented, then data integrity and measurement precision are improved, but device complexity and loss of time increase due to extensive monitoring and analysis requirements
Solution Approach 1:
The patent applies segmentation by dividing the logging system into distinct log fields for different types of information (application identity, change type, timestamp, old values, new values). This segmentation allows the system to track comprehensive changes while organizing data in a manageable, query-friendly structure that reduces analytical complexity.
Solution Approach 2:
The patent implements partial action by logging only the specific fields and changes that are most relevant for maintenance decisions, rather than capturing every possible detail. The system focuses on tracking schema changes, data modifications, and usage patterns that directly impact object maintenance, avoiding unnecessary logging overhead.
3Reliability
If unused objects are not identified and removed, then system stability is maintained through conservative data retention, but storage space increases and productivity decreases due to degraded performance
Solution Approach 1:
The patent applies self-service by enabling the system to automatically identify unused objects through analysis of logged change and usage data. The system generates maintenance recommendations and can automatically remove identified unused objects without requiring manual intervention, thereby maintaining stability through systematic rather than conservative retention policies.
Solution Approach 2:
The patent implements discarding and recovering by systematically identifying objects that are no longer used by any applications and safely removing them from the database. This process recovers storage space and improves performance while maintaining system stability through the protective framework of change logging and analysis that ensures only truly unused objects are removed.
Data Source
AI summary
An approach for tracking system changes to support data maintenance within a directory service environment. Log fields are added to a directory service database for applications that interface with a directory service environment based on predetermined fields to be tracked. The log fields are updated to register database schema fields and data associated with the applications to create a history of changes. An application's identity and data access to the directory service environment are monitored and the log fields are updated to create a history of usage. The directory service database history of usage and changes are periodically analyzed to determine applications relationship dependencies and usage information. Associated maintenance actions are identified by detecting conditions in the directory service environment, based on predetermined maintenance criteria and maintenance is performed.