Primary Data Versioning for Concurrent Simulation Queries
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database systems face challenges in performing simulations due to frequent updates in underlying data, leading to data inconsistencies and difficulties in comparing results, especially when multiple users run simulations concurrently, as current methods require creating copies of data that are resource-intensive and hard to maintain consistency between primary and secondary data stores.
Innovation Solution
Implementing a method that uses version data stores to manage changes by storing multiple versions of data with version identifiers, allowing simulations to be executed using a base primary data version identifier, and merging secondary data with primary data version data to produce a combined simulation dataset, thereby reducing the need for data copying and maintaining consistency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If copies of data are created for simulations, then simulation accuracy is improved, but memory usage and processor requirements increase significantly
Solution Approach 1:
The patent segments data into primary data (stored in version stores) and secondary data (user-specific simulation data). Instead of copying entire data sets, the system separates base data from simulation-specific modifications, allowing simulations to use only necessary data portions while maintaining accuracy.
Solution Approach 2:
The patent introduces version stores as intermediaries between primary data and simulation data. These version stores manage data versions and track changes, enabling simulations to access base data without requiring full data copies, thus reducing memory requirements while maintaining simulation fidelity.
2Adaptability or versatility
If data copies are created for concurrent simulations, then multiple users can run simulations simultaneously, but data consistency between primary and secondary stores becomes difficult to maintain
Solution Approach 1:
The patent implements dynamic version management where data versions are automatically updated and tracked. The system dynamically tracks which data versions are associated with which simulations, allowing concurrent users to access different data versions simultaneously without consistency conflicts.
Solution Approach 2:
The patent uses feedback mechanisms through version tracking and data change logging. When data changes occur, the system feedbacks this information to maintain accurate version records, ensuring that concurrent simulations see consistent data states appropriate to their respective version points in time.
3Reliability
If entire data sets are copied for simulations, then simulation independence is improved, but processing time and resource consumption increase
Solution Approach 1:
The patent extracts only the necessary base data from the entire data set and stores it in version stores. Simulations then load only this extracted base data plus their specific secondary data, rather than copying entire data sets, significantly reducing processing time and resource consumption while maintaining simulation independence.
Solution Approach 2:
Instead of copying entire data sets (excessive action), the patent copies only the necessary base data portions (partial action) that are required for each simulation. This partial copying approach maintains simulation independence while dramatically improving processing efficiency.
Data Source
AI summary
Querying a data set formed from a version of primary data and secondary data is facilitated. First and second versions of primary data are stored in a primary data version store. Secondary data is received. The secondary data is stored in a secondary data store. A query language statement is received. The query language statement is executed by selecting query results from a data set that includes the secondary data and elements of the first version of primary data not inconsistent with the secondary data.