Reorganization of data under continuous workload

• US 10,061,830 B2
• Filed: 03/10/2015
• Issued: 08/28/2018
• Est. Priority Date: 03/15/2010
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Denuit, Bruno H. M., Talius, Tomas
• Primary Examiner(s): Pham, Hung Q
• Application Number:
  US14/643,896
• Publication Number:
  US 20150186490A1
• Time in Patent Office: 1,267 Days
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• CPC Class Codes: G06F 16/278 Data partitioning, e.g. horizontal or vertical partitioning

Abstract

Architecture that provides the capability to automatically (e.g., dynamically) reorganize (repartition) an existing partition by dividing (splitting) or recombining (merging) logical databases. This reorganization can be performed to logical databases belonging to the same customer, and based on the partitioning of the tables in these databases. This can include not only splitting secondary replicas of a partition or merging secondary replicas of the partition, but also splitting off secondary replicas of the partition to create a new partition and merging two partitions into one partition. Moreover, these operations can occur while the logical databases are accepting workload (online).

Claims

1. A computer-implemented database management system, comprising:

a distributed database defined by performance parameters and having a composition of logical database units that provide online data; and

a reorganization component, at least partially implemented by a processor, of a replication component configured to monitor the performance parameters relative to performance limits and perform dynamic adjustment of the composition to increase the logical database units of the composition in accordance with the monitored performance parameters, the dynamic adjustment including a split of a first logical database unit into a second logical database unit and a third logical database unit,

the first logical database unit including a first primary replica and a first secondary replica that is a copy of and receives data modifications from the first primary replica,

the second logical database unit including a second primary replica and a second secondary replica that is a copy of and receives data modifications occurring on the second primary replica and replicates modifications in a first partition key range, and

the third logical database unit including a third primary replica and a third secondary replica that is a copy of and receives data modifications occurring on the third primary replica and replicates modifications in a second partition key range.

2. The computer-implemented database management system of claim 1, wherein the reorganization component is configured to split the first logical database unit into the second logical database unit and the third logical database unit in response to an adverse impact by the at least one change on the database performance.

3. The computer-implemented database management system of claim 1, wherein at least one of the second logical database unit or the third logical database unit receive modifications to data via a replication catch-up operation.

4. The computer-implemented database management system of claim 3, wherein the first, second, and third primary replicas are configured to accept both read and write requests while the first, second, and third at least one secondary replicas are being caught up during the replication catch-up operation.

5. The computer-implemented database management system of claim 1, wherein at least one of the second logical database unit or the third logical database unit receive modifications to data via a replication copy operation that scans source tables relevant to the replica or the partition.

6. The computer-implemented database management system of claim 1, wherein the logical database units operate online to provide continuous access to the data during adjustment by the reorganization component.

7. The computer-implemented database management system of claim 1, wherein the reorganization component is configured to perform the dynamic adjustment of the composition to increase the logical database units of the composition in response to at least one change that impacts database performance.

8. A database management system, comprising:

one or more computer readable storage media storing executable instructions that when executed by a processor provide;

a reorganization component of a replication component configured to monitor performance parameters relative to performance limits and perform dynamic adjustment of a composition of logical database units to increase the logical database units of the composition in accordance with the monitored performance parameters, the dynamic adjustment including a split of a first logical database unit into a second logical database unit and a third logical database unit,

the first logical database unit including a first primary replica and a first secondary replica that is a copy of and receives data modifications from the first primary replica,

the second logical database unit including a second primary replica and a second secondary replica that is a copy of and receives data modifications occurring on the second primary replica and replicates modifications in a first partition key range, and

the third logical database unit including a third primary replica and a third secondary replica that is a copy of and receives data modifications occurring on the third primary replica and replications modifications in a second partition key range.

9. The database management system of claim 8, wherein the reorganization component is configured to split the first logical database unit into the second logical database unit and the third logical database unit in response to an adverse impact by the at least one change on the database performance.

10. The database management system of claim 8, wherein the second logical database unit and the third logical database unit filter received modifications to only allow relevant modifications.

11. The database management system of claim 8, wherein at least one of the second logical database unit or the third logical database unit receives modifications to data via a replication catch-up operation.

12. The database management system of claim 11, wherein the primary replicas are configured to accept both read and write requests while the secondary replicas are being caught up during the replication catch-up operation.

13. The database management system of claim 8, wherein at least one of the second logical database unit or the third logical database unit receives modifications to data via a replication copy operation that only scans source tables relevant to the replica or the partition.

14. The database management system of claim 8, wherein the logical database units operate online to provide continuous access to the data during adjustment by the reorganization component.

15. A computer-implemented database management method that executes on a processor and memory, comprising:

organizing a distributed database as a partition of logical database units;

monitoring parameters associated with performance limits that impact performance of the distributed database; and

dynamically reorganizing a composition of the partition in accordance with the monitored parameters and while the logical database units are online, said dynamically reorganizing comprising splitting a first logical database unit into a second logical database unit and a third logical database unit,

the first logical database unit including a first primary replica and a first secondary replica that is a copy of and receives data modifications from the first primary replica,

the second logical database unit including a second primary replica and a second secondary replica that is a copy of and receives data modifications occurring on the second primary replica and replicates modifications in a first partition key range, and

the third logical database unit including a third primary replica and secondary replica that is a copy of and receives data modifications occurring on the third primary replica and replicates modifications in a second partition key range.

16. The computer-implemented database management method of claim 15, said splitting comprising splitting the first logical database unit into the second logical database unit and the third logical database unit in response to an adverse impact on the database performance.

17. The computer-implemented database management method of claim 15, further comprising filtering modifications to the at least second logical database unit and the third logical database unit to only allow relevant modifications.

18. The computer-implemented database management method of claim 15 further comprising receiving modifications to data via a replication catch-up operation.

19. The computer-implemented method of claim 18, further comprising:

filtering the modifications so that a secondary replica receives only pertinent rows.

20. The computer-implemented database management method of claim 15 further comprising, receiving modifications to data stored in at least one secondary replica via a replication copy operation that only scans source tables relevant to the at least one secondary replica.