# US 2019/0377723 A1 · Tracking change data in a database

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

- Number: US 2019/0377723 A1
- Document ID: US20190377723A1
- Status: Published application
- Kind: A1
- Application number: 16/547,441
- Filed: 2019-08-21
- Published: 2019-12-12
- Earliest claimed: 2014-08-20
- Assignees: Embarcadero Technologies, Inc.
- Applicants: Embarcadero Technologies, Inc.
- Inventors: Charles W. CARO; Sriram BALASUBRAMANIAN; Stephen Peter BALL
- Web page: https://patentgrep.com/patent/US20190377723A1

## CPC

- G06F 16/2365: {Ensuring data consistency and integrity}
- G06F 16/219: {Managing data history or versioning (querying versioned data G06F16/2474; querying temporal data G06F16/2477)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Methods and systems are disclosed for tracking change data in a database. A database, stored at a computer system, is accessed with a plurality of data written to fields in the database, wherein each data in the fields comprises a record header. Data is changed in at least one field of the plurality of data in the database via the computer system, wherein the changing the data changes the record header for the at least one field. A transaction identification (ID) is stored in the record header for each change to the at least one field. A flag is created in the record header signaling the change to the at least one field. Successive versions of the database are linked together such that a subscriber accessing the database can automatically view a current version of the database with the change by accessing the record header and identifying the flag.

## Claims

### Claim 1

A method for tracking change data, said method comprising:
changing data in at least one field of a plurality of data in a database at a computer system, wherein said plurality of data is comprised within a base table of said database, said base table comprising an original state of said plurality of data, wherein said changing said data changes a record header for said at least one field within a change data table of said database, wherein said change data table comprises changes made to said base table, wherein said record header is collocated within said base table and said change data table;
creating a flag in said record header of said data signaling said change to said at least one field within said change data table; and
linking successive versions of said database together such that a subscriber accessing said database can automatically view a current version of said database with said change by accessing said record header of said data and identifying said flag within said record header of said data.

### Claim 2 (depends on 1)

The method as recited in claim 1, wherein said record header comprises a bit array used to indicate how said field has been changed.

### Claim 3 (depends on 2)

The method as recited in claim 2, wherein said bit array comprises at least two bits, wherein a first bit indicates whether said data for said at least one field has been deleted and a second bit indicates whether said data has been inserted or updated.

### Claim 4 (depends on 1)

The method as recited in claim 1, said method further comprising:
storing a transaction identification (ID) in said record header of said data for each change to said at least one field within said change data table.

### Claim 5 (depends on 4)

The method as recited in claim 4, where said transaction ID in said record header comprises a timestamp.

### Claim 6 (depends on 4)

The method as recited in claim 4, wherein subscriptions are employed with said transaction ID to track change data unique to each one of a plurality of users that are able to access said database simultaneously and change said plurality of data.

### Claim 7 (depends on 1)

The method as recited in claim 1, wherein a plurality of users are able to access said database simultaneously and change said plurality of data and wherein a plurality of record headers are able to store change data from each of said plurality of users without requiring a replication of said database and/or rows of said database based on said change.

### Claim 8 (depends on 1)

The method as recited in claim 1, wherein said database employs structured query language (SQL).

### Claim 9 (depends on 1)

The method as recited in claim 1, said method further comprising:
searching said database based on a query wherein said searching employs filters to search said record header to return results for said query based on said change.

### Claim 10

A non-transitory computer readable storage medium having instructions embodied therein that when executed cause a computer system to perform a method for tracking change data, said method comprising:
changing data in at least one field of a plurality of data in a database at a computer system, wherein said plurality of data is comprised within a base table of said database, said base table comprising an original state of said plurality of data, wherein said changing said data changes a record header for said at least one field within a change data table of said database, wherein said change data table comprises changes made to said base table, wherein said record header is collocated within said base table and said change data table;
creating a flag in said record header of said data signaling said change to said at least one field within said change data table; and
linking successive versions of said database together such that a subscriber accessing said database can automatically view a current version of said database with said change by accessing said record header of said data and identifying said flag within said record header of said data.

### Claim 11 (depends on 10)

The non-transitory computer readable storage medium as recited in claim 10, wherein said record header comprises a bit array used to indicate how said field has been changed.

### Claim 12 (depends on 11)

The non-transitory computer readable storage medium as recited in claim 11, wherein said bit array comprises at least two bits, wherein a first bit indicates whether said data for said at least one field has been deleted and a second bit indicates whether said data has been inserted or updated.

### Claim 13 (depends on 10)

The non-transitory computer readable storage medium as recited in claim 10, said method further comprising:
storing a transaction identification (ID) in said record header of said data for each change to said at least one field within said change data table.

### Claim 14 (depends on 13)

The non-transitory computer readable storage medium as recited in claim 13, where said transaction ID in said record header comprises a timestamp.

### Claim 15 (depends on 13)

The non-transitory computer readable storage medium as recited in claim 13, wherein subscriptions are employed with said transaction ID to track change data unique to each one of a plurality of users that are able to access said database simultaneously and change said plurality of data.

### Claim 16 (depends on 10)

The non-transitory computer readable storage medium as recited in claim 10, wherein a plurality of users are able to access said database simultaneously and change said plurality of data and wherein a plurality of record headers are able to store change data from each of said plurality of users without requiring a replication of said database and/or rows of said database based on said change.

### Claim 17 (depends on 10)

The non-transitory computer readable storage medium as recited in claim 10, wherein said database employs structured query language (SQL).

### Claim 18 (depends on 10)

The non-transitory computer readable storage medium as recited in claim 10, the method further comprising:
searching said database based on a query wherein said searching employs filters to search said record header to return results for said query based on said change.

### Claim 19

A computer system comprising:
a non-transitory data storage unit; and
a processor coupled with the non-transitory data storage unit, the processor configured to:
change data in at least one field of a plurality of data in a database at a computer system, wherein said plurality of data is comprised within a base table of said database, said base table comprising an original state of said plurality of data, wherein said changing said data changes a record header for said at least one field within a change data table of said database, wherein said change data table comprises changes made to said base table, wherein said record header is collocated within said base table and said change data table;
create a flag in said record header of said data signaling said change to said at least one field within said change data table; and
link successive versions of said database together such that a subscriber accessing said database can automatically view a current version of said database with said change by accessing said record header of said data and identifying said flag within said record header of said data.

### Claim 20 (depends on 19)

The computer system of claim 19, wherein said record header comprises a bit array used to indicate how said field has been changed, wherein a first bit indicates whether said data for said at least one field has been deleted and a second bit indicates whether said data has been inserted or updated.
