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.

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.

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.

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.

Abstract: In a method for tracking change data, data is changed in a field of a plurality of data in a database at a computer system, where the plurality of data is included within a base table of the database, the base table including an original state of the plurality of data, where changing the data changes a record header for the field within a change data table of the database, where the change data table includes changes made to the base table. A flag is created in the record header of the data signaling the change to the field within the change data table. 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 of the data and identifying the flag within the record header of the data.

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.

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.

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.