Synchronized updates across multiple database partitions

US10534797B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10534797-B2
Application numberUS-201615365693-A
CountryUS
Kind codeB2
Filing dateNov 30, 2016
Priority dateNov 30, 2016
Publication dateJan 14, 2020
Grant dateJan 14, 2020

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A first store and a second store can be configured to store a first partition of a table of a database and a second partition of the table of the database, respectively. A database management system can be configured to at least update at least a first portion of the first partition where the update includes an update to a first primary key column in the first partition and verify that the first primary key column is unique across the first partition and the second partition. A first row having a first primary key value of the first primary key column from the first partition can be deleted, when the first primary key value in the first partition conflicts with a second primary key value of a second primary key column in the second partition.

First claim

Opening claim text (preview).

What is claimed is: 1. A system, comprising: a first store node storing a first partition of a table of a database; a second store node storing a second partition of the table of the database, the second store node being communicatively coupled to the first store node; and a database management system including at least one programmable processor; and a non-transitory machine-readable medium storing instructions that, when executed by the at least one programmable processor, cause the at least one programmable processor to perform operations including updating at least a first portion of the first partition, the updating including an update to a first primary key column in the first partition, verifying that the first primary key column is unique across the first partition and the second partition, and deleting a first row having a first primary key value of the first primary key column from the first partition, when the first primary key value in the first partition is determined to conflict with a second primary key value of a second primary key column in the second partition based on a comparison of the first primary key value to the second primary key value, the comparison resulting in generation of a data object containing conflicting key values, the data object being separate from the first and second partitions and being used to select rows in at least one of the first partition and the second partition for deleting. 2. The system of claim 1 , wherein the operations further comprise updating at least a second portion of the second partition, the update, of the at least the second portion of the second partition including an update to a second primary key value of the second primary key column in the second partition. 3. The system of claim 2 , wherein the operations further comprise verifying that the second primary key value is unique across the first partition and the second partition. 4. The system of claim 3 , wherein the operations further comprise deleting a second row having the second primary key value from the second partition when the second primary key value conflicts with a first primary key value in the first partition. 5. The system of claim 1 , wherein the operations further comprise verifying that the first primary key value is unique across the first partition and the second partition subsequent to the update of the first partition. 6. The system of claim 4 , wherein the operations further comprise verifying that the second primary key value is unique across the first partition and the second partition subsequent to the update of the second partition. 7. The system of claim 1 , wherein the operations further comprise verifying at the first primary key value is unique across the first partition and the second partition using a control flow between the first partition and the second partition, the control flow being separate from a data flow between the first partition and the second partition. 8. The system of claim 1 , wherein the operations further comprise updating at least the first portion of the first partition by adding an additional row having a new primary key value to the first partition. 9. The system method of claim 1 , wherein the operations further comprise updating at least the first portion of the first partition by modifying an existing primary key value in the first partition. 10. The system of claim 8 , wherein the operations further comprise modifying the existing primary key column in the first partition by numerically shifting a value of the primary key values of the existing primary key column. 11. The system of claim 1 , wherein the update of the at least a first portion of the first partition is facilitated by the data object that includes an indication of the updated primary key values in the first partition. 12. The system of claim 1 , wherein the operations further comprise generating a data object that includes an indication of the first row to delete from the first partition. 13. A computer-implemented method, comprising: updating at least a first portion of a first partition of a table of a database in a first store node, the updating of the at least the first portion of the first partition including an update to a first primary key column in the first partition; verifying that the first primary key column is unique across the first partition and a second partition of the table of the database in a second store node, the second store node being communicatively coupled to the first store node; and deleting a first row having a first primary key value of the first primary key column from the first partition, when the first primary key value in the first partition is determined to conflict with a second primary key value of a second primary key column in the second partition based on a comparison of the first primary key value to the second primary key value, the comparison resulting in generation of a data object containing conflicting key values, the data object being separate from the first and second partitions and being used to select rows in at least one of the first partition and the second partition for deleting. 14. The method of claim 13 , further comprising: updating at least a second portion of the second partition, the updating of the at least the second portion of the second partition including an update to a second primary key value of the second primary key column in the second partition. 15. The method of claim 14 , further comprising: verifying that the second primary key value is unique across the first partition and the second partition. 16. The method of claim 15 , further comprising: deleting a second row having the second primary key value from the second partition when the second primary key value conflicts with a first primary key value in the first partition. 17. The method of claim 13 , further comprising verifying that the first primary key value is unique across the first partition and the second partition subsequent to the update of the first partition. 18. The method of claim 16 , further comprising verifying that the second primary key value is unique across the first partition and the second partition subsequent to the update of the second partition. 19. The method of claim 13 , further comprising verifying that the first primary key value is unique across the first partition and the second partition using a control flow between the first partition and the second partition, the control flow being separate from a data flow between the first partition and the second partition. 20. The method of claim 13 , further comprising updating at least the first portion of the first partition by adding an additional row having a new primary key value to the first partition. 21. The method of claim 13 , further comprising updating at least the first portion of the first partition by modifying an existing primary key value in the first partition. 22. The method of claim 21 , further comprising modifying the existing primary key column in the first partition by numerically shifting a value of the primary key values of the existing primary key column. 23. The method of claim 13 , wherein the updating of the at least the first portion of the first partition is facilitated by the data object that includes an indication of the updated primary key values in the first partition. 24. The method of claim 13 , further comprising: generating a data object th

Assignees

Inventors

Classifications

  • Updates performed during online database operations; commit processing · CPC title

  • Ensuring data consistency and integrity · CPC title

  • G06F16/278Primary

    Data partitioning, e.g. horizontal or vertical partitioning · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10534797B2 cover?
A first store and a second store can be configured to store a first partition of a table of a database and a second partition of the table of the database, respectively. A database management system can be configured to at least update at least a first portion of the first partition where the update includes an update to a first primary key column in the first partition and verify that the firs…
Who is the assignee on this patent?
Sap Se
What technology area does this patent fall under?
Primary CPC classification G06F16/278. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Jan 14 2020 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).