Intra-platform data migration

• US 10,157,196 B2
• Filed: 08/12/2015
• Issued: 12/18/2018
• Est. Priority Date: 08/12/2015
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Baker, David Ross, Hirpara, Mitul J., Gonzales, Michael
• Primary Examiner(s): DAYE, CHELCIE L
• Application Number:
  US14/825,073
• Publication Number:
  US 20170046373A1
• Time in Patent Office: 1,224 Days
• Field of Search: 707609, 707626
• CPC Class Codes: G06F 16/214 Database migration support
• CPC Class Codes: G06F 16/23 Updating

Abstract

A data migration system and method operate within a database platform system, which includes first and second databases, to provide data migration between databases. The data migration includes automatically generating a globally unique identifier for each record of the first database, such as upon creation of each record. Records in the second database are updated or inserted according to whether or not records in the second database have globally unique identifiers that correspond to globally unique identifiers of records in the first database.

Claims

1. A database (DB) platform system that includes first and second DBs having respective first and second records, the system comprising:

a processor; and

a memory to store one or more sequences of instructions which, when executed by the processor, cause the processor to;

automatically associate a globally unique identifier (GUID) with each record of the first DB, the GUID of each record comprises a record identifying attribute combined with a data source identifier, the record identifying attribute uniquely identifies a record within the first DB or the second DB, and the data source identifier identifies a source of the record within the first DB or the second DB;

compare GUIDs of records in the first DB to GUIDs of records the second DB;

insert into the second DB first records from the first DB for which no second records in the second DB have corresponding GUIDs;

update in the second DB, in response to insertion of the first records into the second DB, second records for which first records in the first DB have corresponding GUIDs;

insert at least one second record of the second DB into the first DB when a GUID of the at least one second record does not exist in the first DB; and

update at least one first record in the first DB with data of the at least one second record of the second DB when the GUID of the at least one second record does exist in the first DB.

2. The system of claim 1, wherein, to update the second record in the second DB, execution of the one or more sequences of instructions is to cause the processor to:

identify one or more fields in the second record that do not match corresponding fields in the first record; and

conform the one or more fields in the second record to the corresponding fields in the first record.

3. The system of claim 1, wherein execution of the instructions is to cause the processor to generate the GUID automatically for each record of the first DB upon creation of each record.

4. The system of claim 1, wherein the GUID is to be automatically associated with each record of the first DB upon creation of each record.

5. The system of claim 1, wherein one of the first and second DBs is a sandbox DB to operate within an isolated tenant development space of the DB platform system and the other one of the first and second DBs is a tenant DB, the sandbox DB being a copy of the tenant DB used for testing applications for accessing and manipulating tenant data in the tenant DB, and the isolated tenant development space being separate from general operation of the DB platform system.

6. The system of claim 1, wherein the DB platform system is to operate as a multi-tenant DB system, the first and second DBs are of a tenant of the multi-tenant DB system, and the record identifying attribute of the GUID is unique to a tenant of the multi-tenant DB.

20. The system of claim 1, wherein execution of the one or more sequences of instructions is to cause the processor to:

compare GUIDs of records in the first DB to GUIDs of records the second DB;

insert, into the second DB, first records from the first DB for which no second records in the second DB have corresponding GUIDs;

generate a GUID for the first records from the first DB that are to be inserted into the second DB upon creation of the first records in the second DB; and

update in the second DB second records for which first records in the first DB have corresponding GUIDs.

7. A database (DB) platform method, the method comprising:

automatically associating, by a computing device, a globally unique identifier (GUID) with each record of a first DB of a DB platform, the GUID of each record comprises a record identifying attribute combined with a data source identifier, the record identifying attribute uniquely identifies a record within the first DB or the second DB, and the data source identifier identifies a source of the record within the first DB or the second DB;

comparing, by the computing device, GUID of records in the first DB to GUIDs of records a second DB in the DB platform;

inserting, by the computing device, into the second DB first records from the first DB for which no second records in the second DB have corresponding GUIDs;

updating, by the computing device, in the second DB second records for which first records in the first DB have corresponding GUIDs;

inserting, by the computing device, at least one second record of the second DB into the first DB when a GUID of the at least one second record does not exist in the first DB; and

updating, by the computing device, at least one first record in the first DB with data of the at least one second record of the second DB when the GUID of the at least one second record does exist in the first DB.

8. The method of claim 7, wherein updating a second record in the second DB comprises:

identifying, by the computing device, one or more fields in the second record that do not match corresponding fields in the first record; and

conforming, by the computing device, the one or more fields in the second record to the corresponding fields in the first record.

9. The method of claim 7, wherein the method comprises generating, by the computing device, the GUID automatically for each record of the first DB upon creation of each record.

10. The method of claim 7, wherein the GUID is automatically associated with each record of the first or second DB upon creation of each record.

11. The method of claim 7, wherein one of the first and second DBs is a sandbox DB that operates within an isolated tenant development space of the DB platform and the other one of the first and second DBs is a tenant DB, the sandbox DB being a copy of the tenant DB used for testing applications for accessing and manipulating tenant data in the tenant DB, and the isolated tenant development space being separate from general operation of the DB platform.

12. The method of claim 7, wherein the DB platform operates as a multi-tenant DB and which the first and second DBs are of a tenant of the multi-tenant DB system.

19. The method of claim 7, further comprising:

comparing, by the computing device, GUIDs of records in the first DB to GUIDs of records the second DB;

inserting, by the computing device into the second DB, first records from the first DB for which no second records in the second DB have corresponding GUIDs;

generating, by the computing device, a GUID for the first records from the first DB that are to be inserted into the second DB upon creation of the first records in the second DB; and

updating, by the computing device second records in the second DB for which first records in the first DB have corresponding GUIDs.

13. A database (DB) platform system that includes first and second DBs having respective first and second records, the system comprising:

a processor; and

a memory to store one or more sequences of instructions of a dynamic record identifier and one or more sequences of instructions of an update and insert operator, wherein;

the processor is to execute the one or more sequences of instructions of the dynamic record identifier to automatically generate a globally unique identifier (GUID) for each record of the first DB, the GUID of each record comprises a record identifying attribute combined with a data source identifier, the record identifying attribute uniquely identifies a record within the first DB or the second DB, and the data source identifier comprises identifies a source of the record within the first DB or the second DB;

the processor is to execute the one or more sequences of instructions of the update and insert operator to;

update or insert records in the second DB according to whether corresponding records in the first DB are present or not, respectively;

insert at least one second record of the second DB into the first DB when a GUID of the at least one second record does not exist in the first DB; and

update at least one first record in the first DB with data of the at least one second record of the second DB when the GUID of the at least one second record does exist in the first DB.

14. The system of claim 13, wherein the processor is to execute the one or more sequence of instructions of the update and insert operator to:

compare GUIDs of records in the first DB to GUIDs of records the second DB;

insert, into the second DB, first records from the first DB for which no second records in the second DB have corresponding GUIDs; and

update in the second DB second records for which first records in the first DB have corresponding GUIDs.

15. The system of claim 13, wherein the dynamic record identifier is to generate the GUID automatically for each record of the first DB upon creation of each record.

16. The system of claim 13, wherein one of the first and second DBs is to operate within an isolated tenant development space of the DB platform system and the other one of the first and second DBs is a tenant DB, the sandbox DB being a copy of the tenant DB used for testing applications for accessing and manipulating tenant data in the tenant DB, and the isolated tenant development space being separate from general operation of the DB platform system.

17. The system of claim 13, wherein the DB platform system is to operate as a multi-tenant DB system, and the first and second DBs are of a tenant of the multi-tenant DB system.

18. The system of claim 14, wherein the processor is to execute the one or more sequence of instructions of the update and insert operator to:

instruct the dynamic record identifier to generate a GUID the first records from the first DB that are to be inserted into the second DB upon creation of the first records in the second DB.