Dynamically splitting multi-tenant databases

• US 9,015,177 B2
• Filed: 02/15/2013
• Issued: 04/21/2015
• Est. Priority Date: 10/20/2010
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Cahill, Jason M., Hopmann, Alexander, Fox, Eric, Malhi, Balinder, Rosenfield, Zach, Simek, Patrick, Windle, Marc Keith
• Primary Examiner(s): LEROUX, ETIENNE PIERRE
• Application Number:
  US13/768,727
• Publication Number:
  US 20130159344A1
• Time in Patent Office: 795 Days
• Field of Search: 707/10, 707/655, 707/756, 707/805, 711/137
• US Class Current: 707/756
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation

Abstract

An online service includes managed databases that include one or more tenants (e.g. customers, users). A multi-tenant database may be split between two or more databases while the database being split continues processing requests. For example, web servers continue to request operations on the database while content is being moved. After moving the content, tenant traffic is automatically redirected to the database that contains the tenant'"'"'s content.

Claims

1. A method for splitting a database comprising:

determining split content to split from the database that stores content from different tenants;

marking the split content as read only during a move operation of the split content to a different database;

moving the split content to the different database while non-split content in the database continues to receive and process requests for database operations including write operations; and

automatically redirecting requests for the split content to the different database upon completion of moving the split content.

2. The method of claim 1, wherein a size of the database is restricted to a size that fits within a memory of a physical machine that is hosting the database.

3. The method of claim 1, wherein the splitting process of the database occurs in response to a request to defragment the database.

4. The method of claim 1, wherein the splitting process of the database occurs in response to a number of tenants being stored in the database exceeding a number.

5. The method of claim 1, wherein the splitting process of the database occurs in response to a size of the content being stored within the database exceeding a predetermined size.

6. The method of claim 1, wherein determining the split content to move from the database to the different database, comprises dividing the database into approximately equal portions based on the tenant'"'"'s content that is stored in the database and selectively moving at least one of the portions to the different database.

7. The method of claim 1, wherein the splitting process is started automatically in response to an upgrade operation of a farm in a network of the online service.

8. The method of claim 1, further comprising moving all of the content of the database to at least two different databases.

9. The method of claim 1, wherein the splitting process occurs during an upgrade of a SQL server.

10. A computer-readable storage medium, excluding signals, having computer-executable instructions for, comprising:

determining split content to split from the database that stores content from different tenants;

marking the split content as read only during a move operation of the split content to a different database;

moving the split content to the different database while non-split content in the database continues to receive and process requests for database operations including write operations; and

automatically redirecting requests for the split content to the different database upon completion of moving the split content.

11. The computer-readable storage medium of claim 10, wherein a size of the database is restricted to a size that fits within a memory of a physical machine that is hosting the database.

12. The computer-readable storage medium of claim 10, wherein the splitting process of the database occurs in response to at least one of:

a request to defragment the database;

a number of tenants being stored in the database exceeds a number; and

a determination that a size of the content being stored within the database exceeds a predetermined size.

13. The computer-readable storage medium of claim 10, wherein determining the split content to move from the database to the different database, comprises dividing the database into approximately equal portions based on the tenants'"'"' content that is stored in the database and selectively moving at least one of the portions to the different database.

14. The computer-readable storage medium of claim 10, wherein the splitting process is started automatically in response to an upgrade operation of a farm in a network of the online service.

15. The computer-readable storage medium of claim 10, further comprising moving all of the content of the database to at least two different databases.

16. The computer-readable storage medium of claim 10, wherein the splitting process occurs during an upgrade of a SQL server.

17. A system for splitting a database currently in use, comprising:

a network comprising web servers, back-end servers and databases;

a processor and a computer-readable storage medium;

an operating environment stored on the computer-readable medium and executing on the processor; and

a cloud manager operative to;

determining split content to split from one of the database that stores content from different tenants;

marking the split content as read only during a move operation of the split content to a different database;

moving the split content to the different database while non-split content in the database continues to receive and process requests for database operations including write operations; and

automatically redirecting requests for the split content to the different database upon completion of moving the split content.

18. The system of claim 17, wherein the splitting process is performed in response to at least one of:

a request to defragment the database;

a request to add more users to a tenant;

a determination that a size of the content being stored within the database exceeds a predetermined size.

19. The system of claim 17, wherein determining the split content to move from the database to the different database, comprises dividing the database into approximately equal portions that is stored in the database and selectively moving at least one of the portions to the different database.

20. The system of claim 17, wherein the splitting process is started automatically in response to an upgrade operation of a farm in a network of the online service.