Database Merging Using Common Attribute Keys
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional federated CMDB systems face difficulties in merging databases without a key attribute, requiring manual user intervention and burdensome key attribute resetting.
Innovation Solution
A merging apparatus that extracts common attributes from both databases and uses them as alternate keys to merge data, enabling seamless integration even without a pre-defined key attribute.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If a key attribute is set in advance for merging, then merging can be performed automatically, but databases without a key attribute cannot be merged
Solution Approach 1:
The merging apparatus automatically identifies common attributes between databases and uses them as alternate keys for merging, without requiring manual user intervention to set key attributes. The system serves itself by autonomously determining merging criteria based on attribute comparison
Solution Approach 2:
The system dynamically changes the merging parameter from a pre-defined key attribute to an automatically identified common attribute. When a database without a key attribute is detected, the system identifies common attributes between the new database and existing federated databases, then uses these common attributes as alternate keys for merging
2Adaptability or versatility
If a user manually determines identical data, then databases without key attribute can be merged, but user burden increases
Solution Approach 1:
The merging apparatus performs automatic attribute comparison and data matching without requiring manual user intervention. The system independently identifies common attributes, compares attribute values, and determines identical data, eliminating the need for users to manually determine data equivalence
Solution Approach 2:
The system introduces an alternate key mechanism as an intermediary when the original key attribute is unavailable. By identifying common attributes as alternate keys, the system creates a substitute merging criterion that enables automated processing without manual intervention
3Adaptability or versatility
If a user resets the key attribute, then merging can be performed with a new key, but merging must be performed again and user burden increases
Solution Approach 1:
The system performs preliminary identification of common attributes and establishes alternate keys in advance, before merging is required. When a database without a key attribute is detected, the system proactively identifies suitable common attributes and prepares the merging criteria, avoiding the need for later key attribute resetting and re-merging operations
Data Source
AI summary
A merging apparatus includes a first database in which a plurality of attributes including a key attribute that is set in advance as a key for merging is set and a second database in which one or a plurality of attributes excluding the key attribute is set. Furthermore, the merging apparatus checks an attribute that is set in the first database against an attribute that is set in the second database and extracts a common attribute that is set in common in both the first database and the second database. Then, the merging apparatus merges the first database with the second database by determining whether attribute values classified under the extracted common attribute match.