Database Universe Conversion Engine for Multi-Source Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enterprises face challenges in converting data objects from different database platforms, particularly during mergers and acquisitions, where data needs to be accessed and combined across various formats, requiring a labor-intensive manual process to recreate dependent documents in a multi-source database environment.
Innovation Solution
An engine is configured to analyze a single-source database universe, register a new multi-source connection, and regenerate the universe using a universe conversion algorithm, automatic function mapping, and query generation algorithm, eliminating the need for manual re-creation and enabling automatic conversion of data objects from a single-source to a multi-source database environment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual re-creation of dependent documents is performed to convert data objects from single-source to multi-source database environment, then data conversion can be accomplished, but labor intensity and time consumption increase significantly
Solution Approach 1:
The conversion engine automatically performs the conversion process without requiring manual intervention. The system analyzes the single-source database universe, identifies dependencies, and regenes the multi-source universe automatically, allowing the system to serve itself rather than requiring human operators to manually recreate dependent documents
Solution Approach 2:
The engine performs preliminary analysis of the single-source database universe to identify all dependencies, connections, and relationships before executing the conversion. This preliminary action enables the system to prepare the conversion path in advance, avoiding time-consuming manual discovery during the actual conversion process
2Adaptability or versatility
If manual re-creation of dependent documents is performed to convert data objects from single-source to multi-source database environment, then data conversion can be accomplished, but labor intensity increases
Solution Approach 1:
The conversion engine automatically performs the conversion process without requiring manual intervention. The system analyzes the single-source database universe, identifies dependencies, and regenes the multi-source universe automatically, allowing the system to serve itself rather than requiring human operators to manually recreate dependent documents
Solution Approach 2:
The conversion engine acts as an intermediary between the single-source and multi-source database environments. It automatically handles the complex task of analyzing dependencies, mapping relationships, and regening the universe, mediating the conversion process without requiring direct manual intervention from users
3Adaptability or versatility
If existing reports are updated with new data from multiple sources, then data availability improves, but query complexity and processing overhead increase
Solution Approach 1:
The engine segments the conversion process into distinct phases: analyzing connections, identifying tables and views, mapping alias tables, and regening the universe. This segmentation allows each aspect of the multi-source environment to be handled separately and systematically, reducing overall query complexity
Solution Approach 2:
The conversion engine acts as an intermediary that automatically handles query transformation and optimization. It mediates between the multi-source data environment and the reporting system, automatically adjusting queries to work efficiently with the new database structure without requiring manual query rewriting
Data Source
AI summary
Embodiments relate to converting data object(s) from a single-source database environment into a multi-source database environment. An engine is configured to receive a single-source database universe from a repository. The engine analyzes that universe to identify details thereof for conversion, including but not limited to connections, tables, views, alias tables, etc. A new multi-source connection is registered, and then the multi-source universe is re-generated through a universe conversion algorithm, an automatic function mapping algorithm, and a query generation algorithm. Embodiments avoid labor intensive manual re-creation of the universe, and may be implemented as an automatic conversion wizard also updating dependent report queries per new multi-source query patterns. Particular embodiments converting a single-source database environment available from SAP AG, may utilize a Software Design Kit (SDK) to create a migration plug-in as part of an Information Design Tool (IDT).


