Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement Asynchronous Change Data Capture [CORE4378] #4700

Open
firebird-automations opened this issue Mar 29, 2014 · 4 comments
Open

Implement Asynchronous Change Data Capture [CORE4378] #4700

firebird-automations opened this issue Mar 29, 2014 · 4 comments
Labels
component: engine priority: minor type: new feature

Comments

@firebird-automations
Copy link
Collaborator

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
Copy link
Collaborator Author

Modified by: Sean Leyne (seanleyne)

Link: This issue relate to CORE2021 [ CORE2021 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @aafemt

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

@firebird-automations
Copy link
Collaborator Author

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
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component: engine priority: minor type: new feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dyemanov @firebird-automations