Sap Se

Sebastian Haase

Michael Haberkorn

Tobias Karpstein

Alexander Becker

Dennis Alexander Gauss

Andrey Martynov

Systems and methods include detection of changes to data of a plurality of source objects of a source system, replicating the data changes to corresponding ones of the plurality of target objects, and, during the detection of changes to data and the replication of the data changes: detecting a first change to a first source object, identifying a first maintenance event based on the detected first change; determining a first one or more solutions to resolve the first maintenance event; presenting the first maintenance event and the first one or more solutions to resolve the first maintenance event to a user; receiving an indication from the user of a first solution of the first one or more solutions to resolve the first maintenance event; and, in response to the indication, executing the first solution.

Maintenance events in a data replication system

Disclosed herein are system, method, and computer program product embodiments for replicating data from a source database table to a target database table. An embodiment operates by maintaining a master logging table in communication with a source database table and a subscriber logging table. Thereafter, a copy of a first modification of data of the source database table is provided to the master logging table as a record, where the first record includes the copy of the first modification of data. Subsequently, upon determining that the first record in the master logging table is committed, a copy of the first record is provided to the subscriber logging table. And after identifying a first target database associated with the master logging table, the first record is sent to the first target database.

Subscription-based change data capture mechanism using database triggers

Systems and methods to read records of a data staging table, where each record of the data staging table is associated with a package identifier, a key value of a record of a first database table, values of one or more non-key fields of the record of the first database table, and a database operation, include reading of one or more records of the data staging table, each of the read one or more records associated with a package identifier indicating the record is not being processed, and not including a same key value as any other record of the data staging table associated with a package identifier indicating the record is being processed, updating the package identifier of each of the read records of the data staging table to a first package identifier indicating that the record is being processed, creating a transaction record of a transaction queue associating the data staging table and the first package identifier, determining that the read one or more records have been processed, and, in response to the determination, deleting the one or more read rows from the data staging table and the transaction record.

Parallel reads of data staging table

Disclosed herein are system, method, and computer program product embodiments for replicating data from table in a source database to a target database. In some embodiments, data replication includes access plan delimitation and access plan calculation steps and is performed on a table having multiple partitions. A table may be divided into one or more partitions and each partition may be further divided into one or more access plans. Access plan delimitation may involve calculating, in parallel, boundaries of access plans within partitions of the table. Access plan calculation may be initiated on the first partition that has completed the access plan delimitation steps, and may involve transferring data from each delimited partition from the table in the source database to the target database.

Parallel calculation of access plans delimitation using table partitions

Systems and methods include creation of a first target table in a target system, the first target table having a structure of a first source table and loaded with data of the first source table, creation of a view in the target system, the view having a name of the first source table and configured to select from the first target table, reception of a request to reload a current version of the first source table into the target system, and, in response to the request, creation of a second target table in the target system, the second target table having a structure of the current version of the first source table, copying of data of the current version of the first source table to the second target table while the view is configured to select from the first target table, and, after copying of the data of the current version of the first source table to the second target table is complete, modification of the view to select from the second target table.

Growing community of inventors

Kronau, Germany

Sebastian Haase