Cloud Database Dependency Record Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database systems lack efficient mechanisms for tracking and managing object dependencies, particularly in cloud database environments, which hinders proactive identification of impacted views and associated users during changes to tables, and complicates data erasure and trustworthiness assessments.
Innovation Solution
A dependency management system within the cloud database system detects object dependencies created by Data Definition Language (DDL) operations and generates dependency records, which are stored and updated as needed, allowing for real-time tracking and querying of dependency information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If object dependencies are tracked using traditional database mechanisms, then data storage and access are provided, but efficient tracking and management of object dependencies is lacking
Solution Approach 1:
The patent segments dependency tracking into separate dependency records that are independently maintained. Each dependency relationship between database objects (tables, views, procedures) is captured as a discrete record containing the referencing object, referenced object, and dependency type. This segmentation enables efficient querying and management of individual dependency relationships without complicating the overall database structure.
Solution Approach 2:
The patent introduces dependency records as an intermediary layer between database objects and users. These records serve as a mediator that stores and manages dependency information, allowing users to query impact analysis without directly accessing complex database metadata. The dependency records act as a buffer that simplifies the interface between object dependencies and user queries.
2Productivity
If no dependency tracking mechanism is implemented, then system simplicity is maintained, but proactive identification of impacted views and users during table changes is hindered
Solution Approach 1:
The patent implements preliminary action by pre-establishing dependency records whenever database objects are created or modified. When a table is created, altered, or dropped, the system automatically generates and updates dependency records that capture all referencing views, procedures, and other objects. This preliminary tracking enables instant impact analysis without requiring time-consuming queries at the moment of change.
Solution Approach 2:
The patent implements feedback mechanisms where the dependency management system continuously monitors and updates dependency records based on DDL operations. When changes occur in the database schema, the system provides feedback by updating the dependency graph, which then enables rapid impact analysis. This feedback loop ensures that dependency information remains current and accurate for proactive identification of affected objects.
3Loss of information
If comprehensive dependency information is stored, then accurate impact analysis and data erasure compliance are enabled, but data storage requirements increase
Solution Approach 1:
The patent extracts only the essential dependency information needed for impact analysis and compliance tracking. Each dependency record contains specifically the referencing object identifier, referenced object identifier, and dependency type - excluding unnecessary metadata. This extraction approach maintains complete dependency information for operational needs while minimizing storage requirements by storing only what is essential for dependency tracking and impact analysis.
4Ease of operation
If real-time dependency tracking is implemented, then proactive communication of impact to users is enabled, but system complexity and resource consumption increase
Solution Approach 1:
The patent implements self-service where the dependency management system automatically performs impact analysis without requiring complex manual intervention. When a database object is modified, the system autonomously queries the dependency records, identifies all affected objects, and provides impact information. This self-service approach simplifies user operations for impact communication while managing system complexity through automated processes rather than manual procedures.
Data Source
AI summary
Aspects of the present disclosure address systems, methods, and devices for tracking object dependencies in a cloud database system. An object dependency created between a referencing object and a referenced object is detected. Based on detecting the object dependency, a dependency record is generated. The dependency record includes dependency information describing the object dependency between the reference object and the referenced object. The dependency record is stored in a database of dependency records.