Did this article resolve your question/issue?



How to implement CDC (Change Data Capture) with OpenEdge?

« Go Back


TitleHow to implement CDC (Change Data Capture) with OpenEdge?
URL NameHow-to-implement-CDC-Change-Data-Capture-with-OpenEdge
Article Number000176485
EnvironmentProduct: OpenEdge
Version: All supported versions
OS: All supported platforms
Other: CDC, Pro2
Question/Problem Description
How to implement Change Data Capture with OpenEdge?
How does OpenEdge implement CDC (Change Data Capture)?
How is CDC implemented in OpenEdge?
How to replication some tables but not all tables in an OpenEdge database?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
CDC can be implemented in OpenEdge using:
  1. OpenEdge's Pro2 product.  Pro2 can be used to replicate changes from an OpenEdge database to an OpenEdge, MS SQL or Oracle database.  
  2. ABL trigger-based replication.  For information on ABL trigger based replication see:  or 
  3. Changes from SQL can be replicated making use of Java Stored procedures.  For additional information on Java stored procedures see article:  What are Stored Procedures and Triggers?.
  4. Auditing could be enabled and policies defined that would capture changes that would need to be applied to a separate database.  Those captured changes could then be used to replicate changes against another database.
  5. As of OpenEdge 11.7, OpenEdge Change Data Capture is available as an add-on product to the Enterprise or Workgroup RDBMS. Pro2 v5 can be implemented using OE CDC instead of triggers.
For assistance with the use of Pro2 product, creation or use of  ABL trigger-based replication, Java Stored procedures and or the use of auditing data to replicate changes against another database, please engage our Consulting Services or contact your Sales Representative for assistance in engaging Consulting.
Last Modified Date11/20/2020 7:15 AM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.