This larger change introduces LOG_BASED / Change Data Capture (CDC) replication for pipelinewise-tap-mssql.
Features Include:
[ ] Support for MS SQL Server Change Data Capture (CDC) / LOG_BASED replication
[ ] Additional documentation (MS_CDC_SETUP.md) which describes how to enable CDC replication on SQL Server
[ ] Updated README.md for using LOG_BASED replication
[ ] Automatic initial load for tables when using LOG_BASED. After the initial load only changes (Inserts, Update, or Deletes) will be replicated from the last point of replication using the SQL Server LSN as a point of reference.
[ ] Current replication LSN is emitted as a state message to pick-up from the point of the last run
Note: This change does not support change tracking which is an older MS SQL Server replication technology. Change Data Capture is a more efficient and complete solution for incremental replication.
Note: While this change has been well tested and used, it comes with no warranties on guaranteed delivery and zero data loss in replication. It is recommend to test this well and ensure there is a frequent replication within the set archive policy for CDC logs.
This pull request build on top of https://github.com/wintersrd/pipelinewise-tap-mssql/pull/24 . It is a superset of pull request 24.
This larger change introduces LOG_BASED / Change Data Capture (CDC) replication for pipelinewise-tap-mssql.
Features Include:
Note: This change does not support change tracking which is an older MS SQL Server replication technology. Change Data Capture is a more efficient and complete solution for incremental replication.
Note: While this change has been well tested and used, it comes with no warranties on guaranteed delivery and zero data loss in replication. It is recommend to test this well and ensure there is a frequent replication within the set archive policy for CDC logs.