Virtual Database Integration Through Zero-Copy Volumes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database integration technologies cause performance drops due to increased load on database servers and data sources, and ID conflicts arise when integrating databases not designed for integration, leading to inefficiencies and complexity.
Innovation Solution
A virtual integration system that creates a virtual volume for each database, changes database names and schema names to avoid conflicts, and generates integrated tables to manage database areas, allowing zero-copy processing for efficient cross-database searches.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If database integration is performed by copying and consolidating data from multiple databases, then data accessibility and integration capability are improved, but system load increases and performance drops
Solution Approach 1:
The system creates a virtual copy of the distributed database structure through a virtual volume, allowing data to be accessed without physical movement. This virtual copying enables integration capability while avoiding the performance penalty of actual data copying and consolidation operations.
Solution Approach 2:
A virtual volume acts as an intermediary layer between the distributed databases and the access point. This mediator consolidates data access paths without requiring actual data consolidation, thereby improving integration capability while maintaining original system performance.
2Adaptability or versatility
If databases not designed for integration are integrated, then data accessibility is improved, but ID conflicts and system complexity increase
Solution Approach 1:
The virtual volume serves as an intermediary that abstracts away the complexity of integrating databases not designed for integration. It provides a unified access interface that handles ID conflicts and structural differences automatically, enabling cross-database searches without increasing system complexity.
Solution Approach 2:
The system segments the integration function into a separate virtual volume layer, isolating the complexity of handling incompatible database structures from the core databases. This segmentation allows cross-database operations while keeping individual database systems simple and unchanged.
3Adaptability or versatility
If data is moved and consolidated from multiple databases, then integration is achieved, but load on database servers increases
Solution Approach 1:
Instead of moving and consolidating actual data which increases server load, the system creates a virtual copy through a virtual volume. This virtual copying achieves data consolidation capability while eliminating the energy-consuming data movement operations that would increase database server load.
Solution Approach 2:
The system replaces the mechanical process of physically moving and consolidating data with a virtualization approach. This substitution eliminates the computational overhead and energy consumption associated with actual data movement while maintaining consolidation functionality.
Data Source
AI summary
An integration device is configured to execute: mount processing in which a virtual volume is created for each database and mounted to the storage location information; first generation processing in which, from the first table of each of the plurality of devices, the DB name and the storage location information are acquired, second generation processing in which, from the second table of each of the plurality of devices, the schema name, the table name, and the DB area ID are acquired, and third generation processing in which, from the third table of each of the plurality of devices, the DB area ID and the relative file path of the file are acquired, and a third integrated table is generated by associating the changed-to DB name, the DB area ID, and the relative file path with one another for each database.