Database migration sequencing using dynamic object-relationship diagram

• US 10,838,930 B2
• Filed: 09/27/2018
• Issued: 11/17/2020
• Est. Priority Date: 04/05/2018
• Status: Active Grant

• Current Assignee: Accenture Global Solutions Limited (Accenture PLC)
• Original Assignee: Accenture Global Solutions Limited (Accenture PLC)
• Inventors: Shah, Vaibhav, Parihar, Hirendra, Bhandari, Nikhil, Jain, Aniket
• Primary Examiner(s): Frumkin, Jesse P
• Application Number:
  US16/144,470
• Publication Number:
  US 20190311041A1
• Time in Patent Office: 782 Days
• CPC Class Codes: G06F 16/211 Schema design and management
• CPC Class Codes: G06F 16/214 Database migration support
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: G06F 16/289 Object oriented databases

Abstract

A database migration system, according to an example of the present disclosure, builds a dynamic object-relationship model of a database and determines a sequence of data migration for moving data from one database to another. The system may determine a dynamic object-relationship model based on a traversal of the database schema from a root object. The system may determine object attributes for child objects in the object database. In an example, an object attribute may be a relationship between the object and another object, or a property of the object. The system may build a dynamic object-relationship model based on the determined object attributes. The system may also determine a sequence for migrating the objects in the database that does not result in missing objects or missing object attributes based on the dynamic object-relationship model.

Claims

1. A database migration system comprising:

at least one processor to execute machine readable instructions stored on at least one non-transitory computer readable medium, wherein the machine readable instructions are executable by the at least one processor to;

receive a database schema for a first database, the database schema including objects in the first database;

generate a dynamic object-relationship model for each object in the first database starting from a root object, wherein to generate the dynamic object-relationship model for each object, the at least one processor is to;

determine an object attribute of a child object in the first database based on the database schema;

determine whether the object attribute of the child object is a reference to another object in the first database;

in response to determining the object attribute of the child object is the reference to the another object,

determine whether the object attribute of the child object is editable or creatable, including determining if the object attribute of the child object refers to data outside of the child object;

based on a determination that the object attribute of the child object is editable or creatable, determine whether the object attribute of the child object references itself;

classify the child object as a self-related object when the child object references itself, or as a direct cross-related object when the child object does not reference itself;

based on a determination that the object attribute of the child object is non-editable or non-creatable, wherein the object attribute of the child object is non-editable or non-creatable if the object attribute of the child object denotes a parent-child relationship, determine whether the child object is a foreign key of another object;

classify the child object as an indirect cross-related object when the child object is a foreign key, and classify the child object as a parent-child related object when the child object is not a foreign key; and

determine an object sequence for migrating the objects in the first database to a second database according to the dynamic object-relationship model, including prioritizing parents in an identified parent-child relationship followed by siblings of the child object in the identified parent-child relationship.

2. The database migration system of claim 1, wherein the machine readable instructions further comprise instructions executable by the at least one processor to:

migrate the objects in the first database to the second database according to the object sequence.

3. The database migration system of claim 2, wherein the machine readable instructions further comprise instructions executable by the at least one processor to:

update the dynamic object-relationship model for new objects added to the first database after the dynamic object-relationship model is determined;

determine a sequence of migration for the new objects; and

migrate the new objects from the first database to the second database according to the sequence of migration for the new objects.

4. The database migration system of claim 2, wherein the machine readable instructions further comprise instructions executable by the at least one processor to:

determine whether object attributes of the objects after migration in the second database are the same as those in the first database; and

based on the object attributes of the objects after migration in the second database being the same as those in the first database, switch from the first database to the second database for a production database.

5. The database migration system of claim 1, wherein the first database and the second database belong to a same customer relationship management application.

6. The database migration system of claim 1, wherein the first database and the second database belong to different customer relationship management applications.

7. The database migration system of claim 1, wherein the database schema represents objects on a cloud service.

8. A database migration system comprising:

at least one processor to execute machine readable instructions stored on at least one non-transitory computer readable medium, wherein the machine readable instructions are executable by the at least one processor to;

receive a database schema for a first database, the database schema including objects in the first database;

generate a dynamic object-relationship model for the first database for each object starting from a root object;

determine an object sequence for migrating the objects in the first database to a second database based on relationships expressed in the dynamic object-relationship model, including prioritizing parents in an identified parent-child relationship followed by siblings of a child object in the identified parent-child relationship;

update the dynamic object-relationship model for new objects in the first database; and

determine a delta object sequence for migrating the objects in the first database to the second database according to the dynamic object-relationship model.

9. The database migration system of claim 8, wherein to generate the dynamic object-relationship model for the first database for each object starting from the root object, the instructions are executable by the at least one processor to:

determine whether a child object of the root object is a standard object;

based on a determination that the child object of the root object is not a standard object, determine the object attribute of the child object of the root object; and

classify the child object of the root object based on the determined object attribute.

10. The database migration system of claim 8, wherein the first database and the second database belong to the same customer relationship management application.

11. The database migration system of claim 8, wherein the first database and the second database belong to different customer relationship management applications.

12. The database migration system of claim 8, wherein the database schema represents objects on a cloud service.

13. The database migration system of claim 8, wherein the machine readable instructions further comprise instructions executable by the at least one processor to:

migrate the objects in the first database to the second database according to the object sequence.

14. A method for migrating objects from a first database to a second database, the method comprising:

determining an object attribute of a child object based on a database schema;

determine whether the object attribute of the child object is a reference to another object in the first database;

determining whether the object attribute of the child object is editable or creatable including determining if the object attribute of the child object refers to data outside of the child object;

based on the determination that the object attribute of the child object is editable or creatable, determining whether the child object references itself;

classifying the child object as a self-related object when the child object references itself or classifying the child object as a direct cross-related object when the child object does not reference itself;

based on the determination that the object attribute of the child object is non-editable or non-creatable, wherein the object attribute of the child object is non-editable or non-creatable if the object attribute of the child object denotes a parent-child relationship, determining whether the child object is a foreign key of another object;

classifying the child object as an indirect cross-related object when the child object is a foreign key or classifying the child object as a parent-child related object when the child object is not a foreign key;

generating a dynamic object-relationship model for the first database for each object in the database schema starting from a root object; and

determining an object sequence for migrating the objects from the first database to a second database according to the dynamic object-relationship model.

15. The method of claim 14, wherein determining the object sequence comprises determining the object sequence based on relationships expressed in the dynamic object-relationship model.

16. The method of claim 14, wherein the first database and the second database belong to the same customer relationship management application.

17. The method of claim 14, wherein the first database and the second database belong to different customer relationship management applications.

18. The method of claim 14, wherein the database schema represents objects on a cloud service.

19. The method of claim 14, comprising:

updating the dynamic object-relationship model for new objects added to the first database after the dynamic object-relationship model is determined;

determining a sequence of migration for the new objects; and

migrating the new objects from the first database to the second database.

20. The method of claim 14, comprising:

determining whether object attributes of objects from the first database after migration in the second database are the same as those in the first database; and

based on the determining whether the object attributes of objects from the first database after migration in the second database are the same as those in the first database, switching from the first database to the second database for a production database.