PROVISIONING AND/OR SYNCHRONIZING USING COMMON METADATA

• US 20130138612A1
• Filed: 11/29/2011
• Published: 05/30/2013
• Est. Priority Date: 11/29/2011
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Iyer, Ganeshan
• Granted Patent: US 9,031,909 B2
• Time in Patent Office: Days
• US Class Current: 707/638
• 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/93 Document management systems

Abstract

Techniques are described herein that are capable of provisioning and/or synchronizing a data store using common metadata. For instance, a common instance of metadata may be used in lieu of multiple instances of the metadata that correspond to respective items in the data store for indicating a time at which the data store was provisioned. Each time a change occurs with respect to an item in a data table of the data store after provisioning of the data store, a record may be added or updated in a corresponding tracking table. When a request is made for changes that have occurred with respect to the items in a data table, the common instance of the metadata may be used to generate a record in the corresponding tracking table for each item in the data table that did not change since the data store was provisioned.

Claims

1. A method comprising:

provisioning a first data store in a first node for synchronization with a second data store in a second node for a time period that is independent of a size of the first data store, the first data store including a data table that has a plurality of items, the provisioning comprising;

determining a time at which the first data store is provisioned; and

generating a common instance of metadata that is common to the plurality of items to indicate the time at which the first data store is provisioned in lieu of generating a plurality of item-specific instances of the metadata corresponding to the plurality of respective items to indicate the time at which the first data store is provisioned.

2. The method of claim 1, wherein provisioning the first data store further comprises:

generating a tracking table to indicate changes that occur with respect to the plurality of items in the data table since the first data store is provisioned; and

wherein the method further comprises;

synchronizing the first data store with the second data store, the synchronizing comprising;

generating a record of a first type in the tracking table for each item of the plurality of items in the data table that is modified since the first data store is provisioned, each record of the first type indicating a version of the corresponding item that includes a corresponding modification and further indicating a time at which the corresponding item is modified to include the corresponding modification; and

generating a record of a second type in the tracking table for each item of the plurality of items in the data table that is not modified since the first data store is provisioned, based on the common instance of the metadata, to indicate the time at which the first data store is provisioned.

3. The method of claim 2, wherein generating the tracking table comprises:

generating the tracking table to include no records upon completion of the provisioning of the first data store.

4. The method of claim 2, wherein synchronizing the first data store with the second data store further comprises:

providing a copy of the tracking table to the second data store; and

not persisting each record of the second type in the tracking table in response to providing the copy of the tracking table to the second data store.

5. The method of claim 2, wherein generating a record of the second type in the tracking table for each item of the plurality of items in the data table that is not modified comprises:

generating a record of the second type in the tracking table on the fly for each item of the plurality of items in the data table that is not modified.

6. The method of claim 2, wherein the method further comprises:

generating knowledge information that indicates which records of the first type in the tracking table and which records of the second type in the tracking table are provided to each of a plurality of nodes with which the first node is coupled via a network;

determining that each record of the first type in the tracking table has been provided to each of the plurality of nodes; and

deleting each record of the first type from the tracking table in response to determining that each record of the first type has been provided to each of the plurality of nodes.

7. The method of claim 2, wherein the method further comprises:

generating knowledge information that indicates which records of the first type in the tracking table are provided to each of a plurality of nodes with which the first node is coupled via a network, the plurality of nodes including the second node;

determining which records of the first type in the tracking table have been provided to the second node based on the knowledge information;

providing a first subset of the records of the first type to the second node based on each record in the first subset not having been provided to the second node; and

not providing a second subset of the records of the first type to the second node based on each record in the second subset having been provided to the second node.

8. The method of claim 1, wherein generating the common instance of the metadata includes:

generating the common instance of the metadata to identify the first node.

9. The method of claim 1, further comprising:

storing the common instance of the metadata externally to the first data store.

10. A system comprising:

provisioning logic that includes electrical circuitry and is configured to provision a first data store in a first node for synchronization with a second data store in a second node for a time period that is independent of a size of the first data store, the first data store including a data table that has a plurality of items, the provisioning logic comprising;

time logic configured to determine a time at which the first data store is provisioned;

metadata logic configured to generate a common instance of metadata that is common to the plurality of items to indicate the time at which the first data store is provisioned; and

tracking logic configured to generate a tracking table to indicate changes that occur with respect to the plurality of items, the tracking table including no records upon completion of provisioning of the first data store.

11. The system of claim 10, further comprising:

synchronization logic configured to synchronize the first data store with the second data store, the synchronization logic comprising;

first record logic configured to generate a record of a first type in the tracking table for each item of the plurality of items in the data table that is modified since the first data store is provisioned, each record of the first type indicating a version of the corresponding item that includes a corresponding modification and further indicating a time at which the corresponding item is modified to include the corresponding modification; and

second record logic configured to generate a record of a second type in the tracking table for each item of the plurality of items in the data table that is not modified since the first data store is provisioned, based on the common instance of the metadata, to indicate the time at which the first data store is provisioned.

12. The system of claim 11, wherein the synchronization logic further comprises:

provision logic configured to provide a copy of the tracking table to the second data store; and

wherein the second record logic is configured to not persist each record of the second type in the tracking table in response to the copy of the tracking table being provided to the second data store.

13. The system of claim 11, further comprising:

knowledge logic configured to generate knowledge information that indicates which records of the first type in the tracking table and which records of the second type in the tracking table are provided to each of a plurality of nodes with which the first node is coupled via a network;

determination logic configured to determining whether each record of the first type in the tracking table has been provided to each of the plurality of nodes; and

deletion logic configured to delete each record of the first type from the tracking table in response to a determination that each record of the first type has been provided to each of the plurality of nodes.

14. The system of claim 11, further comprising:

knowledge logic configured to generate knowledge information that indicates which records of the first type in the tracking table are provided to each of a plurality of nodes with which the first node is coupled via a network, the plurality of nodes including the second node;

determination logic configured to determine which records of the first type in the tracking table have been provided to the second node based on the knowledge information; and

provision logic configured to provide a first subset of the records of the first type to the second node based on each record in the first subset not having been provided to the second node, the provision logic further configured to not provide a second subset of the records of the first type to the second node based on each record in the second subset having been provided to the second node.

15. The system of claim 10, further comprising:

a third data store configured to store the common instance of the metadata, the third data store being different from the first data store.

16. A computer program product comprising a computer-readable storage medium having computer program logic recorded thereon for enabling a processor-based system to synchronize a first data store in a first node with a second data store in a second node, the computer program product comprising:

a first program logic module for enabling the processor-based system to provision the first data store for synchronization with the second data store for a time period that is independent of a size of the first data store, the first data store including a data table that has a plurality of items, the first program logic module comprising;

time logic for enabling the processor-based system to determine a time at which the first data store is provisioned, and

metadata logic for enabling the processor-based system to generate a common instance of metadata that is common to the plurality of items to indicate the time at which the first data store is provisioned in lieu of generating a plurality of item-specific instances of the metadata corresponding to the plurality of respective items to indicate the time at which the first data store is provisioned; and

a second program logic module for enabling the processor-based system to synchronize the first data store with the second data store, the second program logic module comprising;

first record logic for enabling the processor-based system to generate a record of a first type in a tracking table for each item of the plurality of items in the data table that is modified since the first data store is provisioned, each record of the first type indicating a version of the corresponding item that includes a corresponding modification and further indicating a time at which the corresponding item is modified to include the corresponding modification, and

second record logic for enabling the processor-based system to generate a record of a second type in the tracking table for each item of the plurality of items in the data table that is not modified since the first data store is provisioned, based on the common instance of the metadata, to indicate the time at which the first data store is provisioned.

17. The computer program product of claim 16, wherein the first program logic module comprises:

tracking logic for enabling the processor-based system to generate the tracking table to indicate changes that occur with respect to the plurality of items in the data table, the tracking table including no records upon completion of provisioning of the first data store.

18. The computer program product of claim 16, wherein the second program logic module further comprises:

provision logic for enabling the processor-based system to provide a copy of the tracking table to the second data store; and

wherein the second recording logic enables the processor-based system to discontinue inclusion of each record of the second type in the tracking table in response to provision of the copy of the tracking table to the second data store.

19. The computer program product of claim 16, further comprising:

a third program logic module for enabling the processor-based system to generate knowledge information that indicates which records of the first type in the tracking table and which records of the second type in the tracking table are provided to each of a plurality of nodes with which the first node is coupled via a network;

a fourth program logic module for enabling the processor-based system to determine whether each record of the first type in the tracking table has been provided to each of the plurality of nodes; and

a fifth program logic module for enabling the processor-based system to delete each record of the first type from the tracking table in response to a determination that each record of the first type has been provided to each of the plurality of nodes.

20. The computer program product of claim 16, further comprising:

a third program logic module for enabling the processor-based system to generate knowledge information that indicates which records of the first type in the tracking table are provided to each of a plurality of nodes with which the first node is coupled via a network, the plurality of nodes including the second node;

a fourth program logic module for enabling the processor-based system to determine which records of the first type in the tracking table have been provided to the second node based on the knowledge information; and

a fifth program logic module for enabling the processor-based system to provide a first subset of the records of the first type to the second node based on each record in the first subset not having been provided to the second node, the provision logic further configured to not provide a second subset of the records of the first type to the second node based on each record in the second subset having been provided to the second node.