# US 2012/0254105 A1 · Synchronizing Records Between Databases

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0254105 A1
- Document ID: US20120254105A1
- Status: Published application
- Kind: A1
- Application number: 13/079,027
- Filed: 2011-04-04
- Published: 2012-10-04
- Earliest claimed: 2011-04-04
- Assignees: Microsoft Corporation
- Inventors: Pierre N. Martin; Bryan Dove
- Web page: https://patentgrep.com/patent/US20120254105A1

## CPC

- G06F 16/275: {Synchronous replication}
- G06F 16/23: Updating
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The described implementations relate to synchronizing records between databases. One implementation can cause historical data of a source database to be recorded as entries on a transaction log and can subsequently cause new data of the source database to be recorded on the transaction log in a same manner as the historical data. This implementation can also identify a distinct attribute associated with an individual entry and generate a message that reflects the individual entry.

## Claims

### Claim 1

At least one computer-readable storage medium having instructions stored thereon that, when executed by a computing device, cause the computing device to perform acts, comprising:
causing historical data of a source database to be recorded as entries on a transaction log;
subsequently causing new data of the source database to be recorded on the transaction log in a same manner as the historical data;
identifying a distinct attribute associated with an individual entry; and,
generating a message that reflects the individual entry.

### Claim 2 (depends on 1)

The computer-readable storage medium of claim 1, wherein the causing historical data comprises initially treating the historical data as new data.

### Claim 3 (depends on 1)

The computer-readable storage medium of claim 1, wherein the causing and the subsequent causing comprise tracking data changes and wherein at start-up the historical data is uploaded as a data change and subsequently the new data is treated as a data change.

### Claim 4 (depends on 1)

The computer-readable storage medium of claim 1, wherein the causing and the subsequently causing comprises generating views of historical data and new data from the source database and generating the transaction log from the views.

### Claim 5 (depends on 1)

The computer-readable storage medium of claim 1, wherein the identifying comprises generating the distinct attribute from the data.

### Claim 6 (depends on 1)

The computer-readable storage medium of claim 1, further comprising associating the distinct attribute with the message as metadata.

### Claim 7 (depends on 1)

The computer-readable storage medium of claim 1, wherein the identifying a distinct attribute comprises identifying a patient identifier.

### Claim 8 (depends on 1)

The computer-readable storage medium of claim 1, wherein the message includes the historical data or the new data associated with the individual entry.

### Claim 9 (depends on 1)

The computer-readable storage medium of claim 1, further comprising associating the distinct attribute with the message as metadata.

### Claim 10 (depends on 1)

The computer-readable storage medium of claim 1, wherein the causing historical data and subsequently causing new data comprise utilizing context-neutral processing for conversion into a target format.

### Claim 11 (depends on 1)

The computer-readable storage medium of claim 1, wherein the causing, the subsequent causing, the identifying and the generating are performed on a client side and subsequently sending the message to a server side.

### Claim 12 (depends on 1)

The computer-readable storage medium of claim 1, further comprising queuing the message for processing into a target format based upon the distinct attribute.

### Claim 13 (depends on 12)

The computer-readable storage medium of claim 12, wherein the queuing groups the processing for a set of messages that share the distinct attribute.

### Claim 14

At least one computer-readable storage medium having instructions stored thereon that, when executed by a computing device, cause the computing device to perform acts, comprising:
receiving a message that conveys an individual entry from a transaction log of historical and new database entries; and,
creating a metadata tag for the message that includes a distinct identifier for the individual entry such that processing of the message for uploading in a target database format is organized at least in part based upon the distinct identifier.

### Claim 15 (depends on 14)

The computer-readable storage medium of claim 14, wherein the organized processing comprises grouping multiple entries for processing that share the distinct identifier of a single patient.

### Claim 16 (depends on 15)

The computer-readable storage medium of claim 15, further comprising spreading processing of the multiple entries over multiple parallel paths.

### Claim 17

A system, comprising:
a data acquisition and distribution tool configured to obtain a message relating to changed data in a source database of records, and further configured to identify an identifier associated with the message and to attach the identifier to the message as metadata; and,
wherein the data acquisition and distribution tool is further configured to specify a processing path from a set of available parallel processing paths for converting the changed data into a target format and uploading the converted data into the target format based at least in part on the identifier of the metadata.

### Claim 18 (depends on 17)

The system of claim 17, further comprising a view generation tool configured to generate views of historical entries and new entries of the source database, and a change tracking tool configured to generate a context-neutral transaction log from the views.

### Claim 19 (depends on 18)

The system of claim 18, further comprising a change capture tool configured to generate the message that includes content associated with an individual entry from the context-neutral transaction log.

### Claim 20 (depends on 19)

The system of claim 19, wherein the data acquisition and distribution tool, the view generation tool, and the change capture tool occur on a single computing device.
