Intra-platform data migration
Assigneesalesforce.com, inc.
InventorsDavid Ross Baker, Mitul J. Hirpara, Michael Gonzales
Life of this patent
Estimating the term…
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.
Claims18
A server of a database (DB) platform system, the server comprising:
- a network interface to communicate with a data storage system, the data storage system including a source DB and a target DB;
- and
- a processor system coupled with a memory system and communicatively coupled with the network interface, the memory system to store program code comprising instructions, wherein execution of the instructions by the processor system is to cause the processor system to:
- generate a unique external identifier (external_id) for each record in the source DB;
- cause initiation of data migration of the records in the source DB to the target DB;
- compare external_ids of records in the source DB to external_ids of records the target DB;
- cause insertion, into the target DB, of records from the source DB not having corresponding external_ids in the target DB;
- cause update of records in the target DB with records from the source DB having an external_id in the target DB;
- and
- wherein the external_id of each record comprises a source identifier (source_id) combined with a record identifier (record_id), the source_id identifying a source of a corresponding record in the source DB, and the record_id uniquely identifying the corresponding record in the source DB.
At least one non-transitory computer-readable storage medium (NTCRSM) comprising instructions, wherein execution of the instructions by a processor system of a computing system is to cause the computing system to:
- generate a unique external identifier (external_id) for each record in a source database (DB), the source DB being stored by and included in a data storage system, and the data storage system storing and including a target DB;
- during a data migration process from the source DB to the target DB,
- insert, into the target DB, records from the source DB that do have an external_id in the target DB,
- update records in the target DB using corresponding records in the source DB that have a same external_id, and
- insert, into the source DB, records from the target DB that do have an external_id in the source DB;
- and
- wherein the external_id of each record comprises a source identifier (source_id) combined with a record identifier (record_id), the source_id identifying a source of a corresponding record in the source DB, and the record_id uniquely identifying the corresponding record in the source DB.
A database (DB) platform system, the system comprising:
- a data storage system to store and to include a source DB and a target DB;
- and
- a server communicatively coupled with the data storage system, the server to:
- generate a unique external identifier (external_id) for each record in the source DB;
- initiate data migration of the records in the source DB to the target DB;
- compare external_ids of records in the source DB to external_ids of records in the target DB;
- insert, into the target DB, records from the source DB not having corresponding external_ids in the target DB;
- update records in the target DB with records from the source DB having an external_id in the target DB;
- and
- wherein the external_id of each record comprises a source identifier (source_id) combined with a record identifier (record_id), the source_id identifying a source of a corresponding record in the source DB, and the record_id uniquely identifying the corresponding record in the source DB.
Dependencies are inferred from the claim text.