METHOD FOR DATABASE CONSOLIDATION AND DATABASE SEPARATION

• US 20120124015A1
• Filed: 01/23/2012
• Published: 05/17/2012
• Est. Priority Date: 07/31/2007
• Status: Abandoned Application

• Current Assignee: Eprentise LLC, Siemens AG
• Original Assignee: Eprentise LLC
• Inventors: Abrams, Helene
• Application Number:
  US13/356,303
• Publication Number:
  US 20120124015A1
• Time in Patent Office: Days
• US Class Current: 707/692
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database

Abstract

Methods for consolidating databases while maintaining data integrity are disclosed. A source database and target database are compared, and consolidated, and the consolidated databases are used. In other examples, a database is split to support divested entities.

Claims

1. A method for consolidating at least one source database and one target database, the method comprising:

automatically deriving one of a rule set or code based on an analysis of the source database and target database;

mining database objects based on the derived rule set, wherein mining the database objects comprises dynamically and automatically analyzing and comparing each of the source database objects and values with corresponding target database objects and values, and for each comparison determining which source database objects and target database objects are identical;

automatically reconciling duplicate database objects based on the comparison by merging the duplicate database objects into a single consolidated database object with corresponding metadata based on the derived rules;

automatically reconciling non-duplicate database objects by creating an instance of a consolidated database object with associated metadata based on the derived rules;

posting any unresolved conflicts to a user for reconciliation, and creating an instance of a consolidated database object with associated metadata based on input received from the user;

consolidating the at least one source database and target database based on consolidated metadata, consolidated data values, consolidated business practices, and consolidated business rules, and wherein consolidating the at least one source database and target database comprises a rule that an entity in a given layer never references an entity in a lower level and all references from an entity are on the same or higher levels;

determining the sequence of consolidating data and wherein consolidating data initiates with at least one of the group consisting of seed data, codes data, configuration data and transaction data; and

storing the consolidated database in a memory.

2. The method of claim 1 wherein when the source data value is exactly identical to the target data value, the method further comprises:

mapping the data values of the at least one source database to the data values of the target database, and wherein when the source data values and the target data values are not identical, the method further comprises defining the data values to be included in the consolidated destination database.

3. The method of claim 1 further comprising:

standardizing non-identical data values that have the same contextual meaning or are synonyms wherein standardizing comprises eliminating punctuation or capitalization and standardizing abbreviations, codes, and nomenclature for data values.

4. The method of claim 1 wherein conflicts are resolved using at least one rule using Boolean logic.

5. The method of claim 1 whereby business processes or business rules that create, read, update, or delete (CRUD) each database object are considered similar business processes or rules.

6. The method of claim 5 whereby at least one of the group consisting of business processes or business rules that have the same input and output data and work flows, business processes or business rules that have the predecessor, successor, and parent processes, business processes or business rules that have the same control constructs business processes or business rules that have the same triggering controls, business processes or business rules that have the same conditional controls, business processes or business rules that have the same sequencing controls, business processes or business rules that have the same concurrence controls, business processes or business rules that have the same repetition controls, business processes or business rules that have the same pausing controls, business processes or business rules that have the same resuming controls, and business processes or business rules that have the same exiting controls are considered similar business processes or rules.

7. The method of claim 5 wherein two business processes are equivalent if the business process or business rule share the same context and are defined by at least one of the group consisting of business process or rule type, similar roles in the CRUD matrix, input and output data and work flows, predecessor, successor, and parent processes, and control constructs.

8. The method of claim 1 wherein the target database is associated with at least one of the group consisting of an acquired company and an acquiring company, and wherein the source database is associated with at least one of the group consisting of an acquired company and an acquiring company.

9. A method for separating, dividing, or divesting at least part of a business entity, the method comprising:

identifying criteria for separating, dividing, or divesting database objects;

automatically deriving one of a rule set or code based on an analysis of a source database and the criteria for separating, dividing, or divesting that source database;

mining database objects based on the derived rule set or code, wherein mining the database objects comprises dynamically and automatically analyzing and comparing each of the source database objects and values with the criteria for separating, dividing, or divesting that source database;

identifying source database objects associated with a parent business entity, the source database including source data values; and

automatically copying related database objects from the source based on the derived rule set or code and the criteria for separating, dividing, or divesting that source database;

whereby the source database objects and its related database objects are copied to a target database or to a subset of a target database.