Database fragment cloning and management

• US 7,890,508 B2
• Filed: 08/19/2005
• Issued: 02/15/2011
• Est. Priority Date: 08/19/2005
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Ludeman, John F., Raman, Balan Sethu, Smith, Samuel H., Gerber, Robert H., Krishna, Murali M., Ashwin, Shrinivas, Hamilton, James R.
• Primary Examiner(s): Ali; Mohammad
• Assistant Examiner(s): Ruiz; Angelica
• Application Number:
  US11/207,482
• Publication Number:
  US 20070043749A1
• Time in Patent Office: 2,006 Days
• Field of Search: 707/101, 707/201, 707/20, 707/202, 707/203, 707/204
• US Class Current: 707/736
• CPC Class Codes: G06F 11/2094 Redundant storage or storage space G06F11/2056 takes precedence
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• CPC Class Codes: G06F 16/2343 Locking methods, e.g. distributed locking or locking implementation details
• CPC Class Codes: G06F 2201/80 Database-specific techniques

Abstract

Mechanisms and techniques for database fragment cloning and management are provided. A database object, such as a table, rowset or index, is divided into fragments. Each fragment is cloned to create cloned fragments, which operationally are substantially identical to one another. One or more of the cloned fragments may be designated as a primary cloned fragment for performing database operations or as a secondary cloned fragment for serving as backup. Updates to each fragment are implemented on the primary cloned fragment and are then propagated from the primary cloned fragment to the corresponding secondary cloned fragments. A cloned fragment can go offline, becoming unavailable to be updated. When the cloned fragment returns online, the cloned fragment is refreshed with data included in the primary cloned fragment. While being refreshed, the cloned fragment may continue to be updated. The cloned fragment is eligible to be designated as a primary cloned fragment when the refreshing process has been completed.

Claims

1. One or more device-readable storage media with device-executable instructions for performing steps comprising:

creating a primary cloned fragment associated with a subset of records in a database table, the primary cloned fragment having a first plurality of records;

adding a first plurality of update identifiers to the primary cloned fragment, wherein each of the first plurality of update identifiers is a member of one of the first plurality of records;

in response to a secondary cloned fragment being offline during an update, preserving an update in the primary cloned fragment;

identifying the secondary cloned fragment corresponding to the primary cloned fragment, the secondary cloned fragment being stale relative to the primary cloned fragment and the secondary cloned fragment having a second plurality of records and a second plurality of update identifiers, wherein each of the second plurality of update identifiers is a member of one of the second plurality of records;

refreshing the stale secondary cloned fragment with the preserved update when the stale secondary cloned fragment returns online by performing a database operation, wherein the refreshing step further comprises;

identifying a first update identifier of a first record in the first plurality of records included in the primary cloned fragment;

identifying a second update identifier of a second record in the second plurality of records in the stale secondary cloned fragment, the second record corresponding to the first record; and

determining whether the first record and second record with identical cloned record identifiers are consistent based, at least in part, on whether the first update identifier and the second update identifier are equal and while refreshing the stale secondary cloned fragment;

performing an update to the primary cloned fragment; and

updating the stale secondary cloned fragment in response to the performing the update on the primary cloned fragment.

2. The one or more device-readable storage media as recited in claim 1, wherein the updating step further comprises updating up-to-date rows of the stale secondary cloned fragment, but not updating any non-up-to-date rows of the stale secondary cloned fragment.

3. The one or more device-readable storage media as recited in claim 1, wherein the refreshing step further comprises, when the first and second records are determined to be inconsistent,

refreshing the second record with data in the first record;

and

assigning a value of the first update identifier to the second update identifier.

4. The one or more device-readable storage media as recited in claim 3, further comprising performing the determining, refreshing and assigning steps for each record of the second plurality of records included in the secondary cloned fragment.

5. The one or more device-readable storage media as recited in claim 1, wherein the refreshing step further comprises running a pre-refreshing operation on the secondary cloned fragment in a read committed mode.

6. The one or more device-readable storage media as recited in claim 5, wherein the pre-refreshing operation is run in parallel on other secondary cloned fragments corresponding to the primary cloned fragment.

7. The one or more device-readable storage media as recited in claim 1, wherein the database operation for refreshing the secondary cloned fragment includes Data Manipulator Language (DML) operations of inserting, deleting and updating records in the secondary clone.