Database File System Flashback Archive Version Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database file systems face challenges in efficiently tracking and retrieving version information of files over time, requiring complex queries and significant overhead, especially in industries that need to maintain chain of custody and privileges for data files.
Innovation Solution
A database file system architecture that incorporates a transaction-based archiving mechanism, allowing the DBMS to generate a set of version identifiers by executing additional queries for metadata related to archive information, and using flashback queries to retrieve prior temporal states of files, thereby automating the retrieval of file versions within the database.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If complex database queries are used to retrieve file version information, then version tracking capability is improved, but system overhead and complexity increase
Solution Approach 1:
The patent segments version information retrieval into two distinct components: metadata queries for version identifiers and flashback queries for actual file state retrieval. This segmentation allows the system to efficiently track versions through metadata while keeping complex flashback operations separate and optimized, reducing overall system complexity while maintaining complete version tracking capability.
Solution Approach 2:
The patent implements preliminary action by maintaining metadata about file versions in advance, including version identifiers and timestamps. This preliminary metadata storage enables quick identification of version states without requiring complex queries at retrieval time, as the system has already organized version information in a query-optimized structure during file modification operations.
2Measurement precision
If manual querying of prior file states is performed, then version retrieval accuracy is improved, but time consumption and labor increase
Solution Approach 1:
The patent introduces metadata as an intermediary layer between the file system and the version retrieval process. This metadata contains pre-computed version identifiers and timestamps that act as a bridge, allowing the system to quickly locate and retrieve specific file versions without performing complex manual queries. The intermediary metadata structure preserves retrieval accuracy while dramatically reducing query execution time.
Solution Approach 2:
The patent creates simplified copies of version information in the form of metadata records that contain essential version identifiers and timestamps. These metadata copies enable rapid version identification without requiring access to the actual file data, allowing the system to quickly determine which version to retrieve while maintaining accurate version information tracking.
3Loss of information
If change management services track all data changes, then chain of custody tracking is improved, but system overhead increases
Solution Approach 1:
The patent extracts only the essential chain of custody information (version identifiers, timestamps, and modification metadata) from complete file change data. By taking out only the critical metadata needed for chain of custody tracking rather than tracking all file change details, the system maintains accurate chain of custody information while significantly reducing the overhead associated with comprehensive change management services.
Data Source
AI summary
A method for generating a query for version information on a file stored a database file system that is managed by a database server. When a client on a remote client machine sends a file operation request, the database management system, receives the file operation request and creates a database query for the requested file operation and an additional query for a set of version identifiers that identify the previous versions of the requested file of the requested file operation. The database management system executes the queries and generates a set of version identifiers, where each identifier from the set of version identifiers represents a specific version of the requested file at a particular point in time in the past.