Condensing event markers
US-2015347497-A1 · Dec 3, 2015 · US
US9305070B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9305070-B2 |
| Application number | US-201213821624-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 31, 2012 |
| Priority date | Dec 31, 2012 |
| Publication date | Apr 5, 2016 |
| Grant date | Apr 5, 2016 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A system, method and computer-readable medium for data capture for replication are provided. A data record from a transaction log of a source database indicative of a data element change is retrieved. A DDL command is generated from the retrieved data record. Once generated, the DDL command is distributed for replication to a target database such that the source database and the target database are synchronized.
Opening claim text (preview).
What is claimed is: 1. A method for data capture for replication, comprising: retrieving a plurality of data records from a source database, wherein at least one data record is retrieved from a first log associated with the source database and at least one data record is retrieved from a second log associated with the source database; parsing a first identifier included in the at least one retrieved data record from the first log and a second identifier included in the at least one retrieved data record from the second log to determine a data element change in the source database, wherein the first and second identifiers are indicative of the data element change and the first and second identifiers cannot be parsed by a target database; and generating a data definition language (DDL) command from the determined data element change, wherein the generated DDL command is compatible with the target database. 2. The method of claim 1 , further comprising: distributing the generated DDL command to the target database to synchronize the source database and the target database. 3. The method of claim 1 , wherein retrieving the plurality of data records further comprises using an application programming interface associated with the source database. 4. The method of claim 1 , wherein at least one data record of the plurality of data records includes a change in at least one column in the data element, wherein the data element includes at least a table or a schema. 5. The method of claim 1 , wherein at least one data record of the plurality of data records includes a change in quantity of columns or schemas in the source database. 6. The method of claim 1 , wherein the first log is a data management system log and the second log is a data object manager log. 7. The method of claim 1 , further comprising: storing the generated DDL command. 8. A system comprising: a memory configured to store modules comprising a replication agent module configured to: retrieve a plurality of data records from a source database, wherein at least one data record is retrieved from a first log associated with the source database and at least one data record is retrieved from a second log associated with the source database; parse a first identifier included in the at least one retrieved data record from the first log and a second identifier included in the at least one retrieved data record from the second log to determine a data element change in the source database, wherein the first and second identifiers are indicative of the data element change and the first and second identifiers cannot be parsed by a target database; and generate a data definition language (DDL) command from the determined data element change, wherein the generated DDL command is compatible with the target database; and one or more processors configured to execute the replication agent module. 9. The system of claim 8 , wherein the replication agent module is further configured to distribute the generated DDL command to the target database to synchronize the source database and the target database. 10. The system of claim 8 , wherein the replication agent module is further configured to use an application programming interface associated with the source database to retrieve the plurality of data records. 11. The system of claim 8 , wherein at least one data record of the plurality of data records includes a change in at least one column in the data element, wherein the data element includes at least a table or a schema. 12. The system of claim 8 , wherein at least one data record of the plurality of data records includes a change in quantity of columns or schemas in the source database. 13. The system of claim 8 , wherein the first log is a data management system log and the second log is a data object manager log. 14. The system of claim 8 , wherein the replication agent module is further configured to store the generated DDL command in a replication agent system database (RASD). 15. A non-transitory computer readable medium having instructions stored thereon that, when executed by a computing device, cause the computing device to perform operations for data capture for replication, the operations comprising: retrieving a plurality of data records from a source database, wherein at least one data record is retrieved from a first log associated with the source database and at least one data record is retrieved from a second log associated with the source database; parsing a first identifier included in the at least one retrieved data record from the first log and a second identifier included in the at least one retrieved data record from the second log to determine a data element change in the source database, wherein the first and second identifiers are indicative of the data element change and the first and second identifiers cannot be parsed by a target database; and generating a data definition language (DDL) command from the determined data element change, wherein the generated DDL command is compatible with the target database. 16. The non-transitory computer readable medium of claim 15 , further comprising: distributing the generated DDL command to the target database to synchronize the source database and the target database. 17. The non-transitory computer readable medium of claim 15 , wherein the first log is a data management system log and the second log is a data object manager log. 18. A method for replication to synchronize databases, comprising: retrieving a first data record from a first log of a source database and a second data record from a second log of the source database, wherein the first data record includes a first identifier, the second data record includes a second identifier, the first identifier and second identifier indicate a data element change in the source database, and the first identifier and the second identifier cannot be parsed by a target database; generating a data definition language (DDL) command from the first data record using the first identifier and the second data record using the second identifier, wherein the generated DDL command is compatible with a target database; and executing the generated DDL command on the target database to synchronize the target database with the source database.
Physics · mapped topic
Physics · mapped topic
Physics · mapped topic
Schema design and management · CPC title
Information retrieval; Database structures therefor; File system structures therefor · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.