Database scale-out

• US 9,189,503 B2
• Filed: 12/06/2012
• Issued: 11/17/2015
• 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:
  US13/707,037
• Publication Number:
  US 20140164443A1
• Time in Patent Office: 1,076 Days
• Field of Search: 707/707, 707/610, 707/620, 707/638, 707/634, 707/E17.005, 707/E17.032, 707/809, 707/613, 707/611, 707/827, 707/687, 707/633, 707/649, 707/812, 707/636, 707/964, 707/971, 707/637, 707/674, 707/803, 707/790, 707/E17.007, 707/E17.055, 707/617, 707/714, 707/718, 707/E17.054, 707/E17.017, 709/201, 709/223, 709/206, 709/208, 709/217, 714/54, 714/100, 719/328
• US Class Current: 1/1
• 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 method for scaling out database information stored on a first database comprising a first data range, the method comprising:

creating, by a computing device, an instantiation of a second database;

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

configuring the second database for receiving the 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; and

designating the second data range as changing;

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

deleting data on the first database associated with the transferred one or more first database partitions without deleting the transferred one or more first database partitions from the second database.

2. The method of claim 1, wherein configuring one or more partitions of the first database includes identifying a first data sub-range for the first database, the first data sub-range including the one or more first database partitions.

3. The method of claim 2, further including designating the first data sub-range as read only.

4. The method of claim 3, wherein configuring the second database includes extending a range of the second database to at least the range of the first data sub-range.

5. The method of claim 2, wherein transferring the one or more first database partitions includes transferring, to the second database, data associated with key values representing a start point and an end point of the first data sub-range.

6. The method of claim 5, further including, upon transferring the key values, changing the mode of the second data sub-range to read-only and changing the mode of the first data sub-range to deleted.

7. The method of claim 6, further including, upon changing the mode of the first data sub-range, removing the second data sub-range on the second database, wherein removing the second sub-range changes the data mode of contained data to read-write.

8. The method of claim 7, further including clearing the first data sub-range on the source database, wherein the clearing causes the source database data range to contract to exclude the first data sub-range.

9. The method of claim 1, further including receiving an alert message from the first database, the alert message indicating that the first database is reaching capacity.

10. A system for performing 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;

creating an instantiation of a second database, the second database instantiation based in part on the first database reaching capacity;

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

configuring the second database for receiving the 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; and

designating the second data range as changing;

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

deleting data on the first database associated with the transferred one or more first database partitions without deleting the transferred one or more first database partitions from the second database.

11. The system of claim 10, wherein configuring one or more partitions of the first database includes identifying a first data sub-range for the first database, the first data sub-range including the one or more first database partitions.

12. The system of claim 11, further comprising designating the first data sub-range as read only.

13. The system of claim 11, wherein transferring the one or more first database partitions includes transferring, to the second database, data associated with key values representing a start point and an end point of the first data sub-range.

14. The system of claim 13, further comprising, upon transferring data associated with the key values, changing the mode of the second data sub-range to read-only and changing the mode of the first data sub-range to deleted.

15. The system of claim 14, further comprising, upon changing the mode of the first data sub-range, removing the second data sub-range on the second database, wherein removing the second sub-range changes the data mode of contained data to read-write.

16. The system of claim 14, further comprising, clearing the first data sub-range on the source database, wherein the clearing causes the source database data range to contract to exclude the first data sub-range.

17. The system of claim 10, wherein configuring the second database includes extending a range of the second database to at least the range of the first data sub-range.

18. The system of claim 10, further comprising receiving an alert message from a first database, the alert message indicating that the first database is reaching capacity.

19. The system of claim 10, wherein creating the second data range includes initiating the creation of a log entry comprising action attributes associated with the database scale-out.

20. A computer-readable medium comprising executable instructions that, when executed by a processor, provide database scale-out, the computer-readable medium including instructions executable by the processor for:

receiving an alert message from a first database, the alert message indicating that the first database is reaching capacity;

creating a first data sub-range for the first database, the first data sub-range having a read only mode;

extending a range of a second database to at least the range of the first data sub-range;

creating a second data sub-range on the second database, the second data sub-range having a changing mode, the second data sub-range created at a database location adjacent to the first data sub-range;

transferring data associated with key values representing a start point and an end point of the first data sub-range start and end points to the second database;

changing the mode of the second data sub-range to read-only;

changing the mode of the first data sub-range to deleted;

removing the second data sub-range on the second database, wherein removing the second sub-range changes the data mode of contained data to read-write;

deleting the data on the first database associated with the key values; and

clearing the first data sub-range on the source database, wherein the clearing causes the source database data range to contract to exclude the first data sub-range.