US 12,450,254 B2
Database data replication tool
Yoann Baumert, Nanterre (FR); Clement Delaunay, Nanterre (FR); and Daniel-Florin Chis, Nanterre (FR)
Assigned to ADP, Inc., Roseland, NJ (US)
Filed by ADP, INC., Roseland, NJ (US)
Filed on Feb. 24, 2023, as Appl. No. 18/113,982.
Application 18/113,982 is a continuation of application No. 17/099,059, filed on Nov. 16, 2020, abandoned.
Prior Publication US 2024/0020314 A1, Jan. 18, 2024
Int. Cl. G06F 15/16 (2006.01); G06F 9/455 (2018.01); G06F 9/50 (2006.01); G06F 16/22 (2019.01); G06F 16/23 (2019.01); G06F 16/25 (2019.01); G06F 16/27 (2019.01)
CPC G06F 16/27 (2019.01) [G06F 9/45558 (2013.01); G06F 9/5016 (2013.01); G06F 9/5083 (2013.01); G06F 16/2282 (2019.01); G06F 16/2358 (2019.01); G06F 16/258 (2019.01); G06F 2009/45583 (2013.01)] 18 Claims
OG exemplary drawing
 
1. A system for data replication, comprising:
one or more processors, coupled with memory, to:
import, through an application programming interface (API), a first plurality of data instances from a source database associated with a system of record (SoR) application;
filter, based on a scope defined by a user, the first plurality of data instances to generate a second plurality of data instances;
automatically execute, using a data replication tool, responsive to filtering the first plurality of data instances based on the scope defined by the user, an individual data replication process for each data instance of the second plurality of data instances at a scheduled time slot to generate a plurality of replicated data instances;
push, responsive to the automatic execution of the individual data replication process for each data instance of the second plurality of data instances at the scheduled time slot, a status of each data instance of the second plurality of data instances to a live stream chat integrated with the data replication tool;
detect, responsive to pushing the status of each data instance of the second plurality of data instances to the live stream chat, a difference between a first data description language (DDL) that defines a structure of a first replicated data instance of the plurality of replicated data instances and a second DDL that defines a structure of a target database;
identify, responsive to detection of the difference between the first DDL and the second DDL, a model, stored as a query language, built to translate the first DDL to the second DDL;
translate, using the identified model, the first DDL of the first replicated data instance to match the second DDL of the target database;
export, based on the translation of the first DDL to match the second DDL, the first replicated data instance to the target database; and
persist, using the API responsive to exporting the first replicated data instance to the target database, database configuration information in a non-relational database, wherein the database configuration information comprises at least one of a status of the target database, an owner of the target database, a last time a last action has been performed with the target database, an indication of a user that performed the last action.