Database scale-out

• US 9,754,008 B2
• Filed: 11/02/2015
• Issued: 09/05/2017
• Est. Priority Date: 12/06/2012
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Genc, Goksel, Guadarrama, Humberto Lezama, Chang, Gary, Watson, Andrew Sean
• Primary Examiner(s): Ly, Anh
• Application Number:
  US14/930,438
• Publication Number:
  US 20160055227A1
• Time in Patent Office: 673 Days
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: G06F 16/214 Database migration support
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 16/278 Data partitioning, e.g. horizontal or vertical partitioning

Abstract

A method for scaling out database information may include creating second database instantiation. The method may include configuring one or more partitions of a first database for transfer to the second database and configuring the second database for receiving the one or more first database partitions. The method may also include transferring the one or more first database partitions to the second database.

Claims

1. A system for providing database scale-out for a first database comprising a first data range, the system comprising:

at least one processor; and

memory coupled to the at least one processor, the memory comprising computer executable instructions that, when executed by the at least one processor, performs a method comprising;

configuring a second database for receiving one or more first database partitions, wherein configuring the second database comprises;

creating a second data range on the second database at a location substantially adjacent to the first data range, wherein the second data range is extended to at least a range of the first data range; and

designating the second data range as changing;

transferring the one or more first database partitions to the second database; and

generating a data transfer history, the data transfer history comprising operations performed while transferring the one or more first database partitions.

2. The system of claim 1, wherein transferring the one or more first database partitions comprises transferring data associated with key values representing a start point and an end point of the first data range to the second database.

3. The system of claim 2, wherein transferring the one or more first database partitions comprises further comprises:

designating the first data range as deleted and designating the second data range as read-only.

4. The system of claim 3, further including, after designating the first data range as deleted, deleting the second data range on the second database, wherein deleting the second range designates the data associated with key values to read-write.

5. The system of claim 1, wherein the data transfer history further comprises information needed to restore at least one of the first database and the second database.

6. The system of claim 5, further comprising:

storing the data transfer history on at least one of the first database and the second database, and using the information to restore data on at least one of the first database and the second database.

7. The system of claim 5, wherein the information comprises a location to at least a third data range.

8. The system of claim 1, the method further comprising, after transferring the one or more first database partitions to the second database, removing the first data range from the first database, wherein removing the first data range from the first database does not include deleting the data associated with the key values from the second database.

9. A method for scaling out database information stored on a first database comprising a first data range, the method comprising:

configuring a second database for receiving one or more first database partitions, wherein configuring the second database comprises;

creating a second data range on the second database at a location substantially adjacent to the first data range, wherein the second data range is extended to at least a range of the first data range; and

designating the second data range as changing; and

transferring the one or more first database partitions to the second database, wherein the transferring is subject to one or more runtime rules.

10. The method of claim 9, further comprising:

creating an instantiation of a second database; and

configuring one or more partitions of the first database for transfer to the second database.

11. The method of claim 10, wherein the instantiation of a second database is created in response to a message received at the first database, the message comprising information about a capacity of the first database.

12. The method of claim 9, wherein the data range is a range of binary key values that are associated with a start point and an end point.

13. The method of claim 9, wherein the one or more first database partitions comprise a weight attribute, the weight attribute corresponding to an amount of data in the one or more first database partitions.

14. The method of claim 9, wherein the first data range is assigned a mode, the mode dictating a runtime behavior of the data in the first data range.

15. The method of claim 14, wherein the mode determines a data access condition for the first data range.

16. The method of claim 9, wherein the first database provides a message comprising a total count and a total weight of the one or more first database partitions.

17. The method of claim 9, further comprising:

designating a mode of the first data range as deleted, and deleting the first data range from the first database.

18. The method of claim 9, further comprising:

after transferring the one or more first database partitions to the second database, removing the first data range from the first database, wherein removing the first data range from the first database does not include deleting the data associated with the key values from the second database.

19. The method of claim 9, wherein at least one of the one or more runtime rules prevents writing data to the first data range when the second data range is designated as changing.

20. A method for scaling out database information stored on a first database comprising a first data range, the method comprising:

configuring a second database for receiving one or more first database partitions, wherein configuring the second database comprises;

creating a second data range on the second database at a location substantially adjacent to the first data range, wherein the second data range is extended to at least a range of the first data range; and

designating the second data range as changing;

transferring the one or more first database partitions to the second database;

generating a data transfer history, the data transfer history comprising operations performed while transferring the one or more first database partitions; and

storing the data transfer history on at least one of the first database and the second database.