Implement Asynchronous Change Data Capture [CORE4378]

[firebird-automations]

Submitted by: Valdir Stiebe Junior (ogecrom)

Relate to CORE2021

Votes: 2

If you ever think about the built-in replication feature request (#⁠CORE2021), please take the time to think about asynchronous change data capture.

ORACLE - http://docs.oracle.com/cd/B19306_01/server.102/b14223/cdc.htm SQL Server - http://technet.microsoft.com/en-us/library/bb522489(v=SQL.105).aspx

Synchronous Change Data Capture is easily achieved using normal table triggers under the performance penalty. So I think it isn't worth the time. Today we use an AUDIT table that receives all the data generated by triggers. An hourly process download the data to another database using "on external datasource" feature.

[firebird-automations]

Modified by: Sean Leyne (seanleyne)

Link: This issue relate to [CORE2021](https://github.com/FirebirdSQL/firebird/issues?q=CORE2021+in%3Atitle) \[ [CORE2021](https://github.com/FirebirdSQL/firebird/issues?q=CORE2021+in%3Atitle) \]

[firebird-automations]

Commented by: @aafemt

Oracle declared CDC deprecated: http://docs.oracle.com/cd/E16655_01/server.121/e17642/deprecated.htm#UPGRD60083

[firebird-automations]

Commented by: Valdir Stiebe Junior (ogecrom)

Just for the record. They repackaged it as a new product: http://www.oracle.com/technetwork/middleware/goldengate/documentation/index.html

[dyemanov]

Firebird 4.0 allows to create custom replication plugins, they can be used for CDC purposes. Future versions will also have a tool to "pretty-print" the replication journal in the text format, so that it could be parsed by external tools that could send changes elsewhere. The plugin-based solution is superior though, IMO.