Virtual Database Data Integration for Multi-Source Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data integration techniques using a single cube are inadequate for handling inconsistent data across multiple business systems, leading to increased costs, information loss, and difficulty in providing real-time analysis, as they require extensive data duplication and reconstruction, which is not feasible for complex corporate analyses.
Innovation Solution
A data retrieval tool that integrates a virtual database with a Business Intelligence (BI) tool, using a single data dictionary to manage data associations across multiple databases, allowing for flexible data integration and analysis without duplicating data, and enabling real-time reporting and analysis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data are consolidated into a single cube for OLAP analysis, then data completeness and consistency are improved, but device complexity and data management costs increase significantly
Solution Approach 1:
The patent divides the data consolidation process into multiple cubes, each representing a specific business system or data source. Instead of creating one monolithic cube, the system segments data into separate cubes that can be independently managed, reducing overall complexity while maintaining data completeness through the virtual database's ability to query across multiple cubes.
Solution Approach 2:
The virtual database acts as an intermediary layer between the user and multiple physical databases/cubes. It provides a unified query interface that automatically joins data from multiple sources without requiring manual data consolidation, thereby reducing data management complexity while maintaining data completeness.
2Productivity
If data are duplicated across multiple systems for analysis, then data availability is improved, but loss of substance and storage costs increase
Solution Approach 1:
Instead of physically duplicating data across multiple systems, the patent uses virtual copying through the virtual database. The system creates virtual representations of data from multiple cubes that can be queried simultaneously, providing data availability for analysis without actual data duplication and storage redundancy.
3Reliability
If extensive data reconstruction is performed for integration, then data consistency is improved, but loss of time and processing costs increase
Solution Approach 1:
The system performs preliminary data organization by structuring data into standardized cubes with consistent schemas before analysis. Each cube is pre-configured with proper data types, relationships, and metadata, so that when the virtual database queries across cubes, data consistency is already established without requiring extensive reconstruction during analysis.
Solution Approach 2:
The patent replaces manual data reconstruction processes with automated virtual database queries. Instead of mechanically joining and reconciling data from multiple sources through complex ETL processes, the system uses SQL-like queries that automatically handle data retrieval and joining across multiple cubes, significantly reducing processing time while maintaining consistency.
4Ease of operation
If a single cube structure is used for multi-dimensional analysis, then analysis simplicity is improved, but adaptability to handle inconsistent data from multiple sources deteriorates
Solution Approach 1:
The virtual database provides a universal query interface that can access and analyze data from multiple different cube structures simultaneously. It supports multi-dimensional analysis across cubes with different schemas and data sources, maintaining analysis simplicity while adapting to diverse data structures through standardized query processing.
Data Source
AI summary
A data retrieval apparatus includes a processor, and a memory. The memory stores a virtual database that analyzes a retrieval request input from a user terminal to generate a retrieval instruction, executes the generated retrieval instruction in the database to acquire two or more retrieved data, and integrates the acquired two or more retrieved data to prepare a retrieval result responding to the retrieval request.


