Someone was asking about MSSQL and CDC. Just stumbled on https://docs.microsoft.com/en-us/sql/relational-databases/track-changes/about-change-data-capture-sql-server?view=sql-server-ver15 , should work I'd think for Log based replication

Yeah - we used log-based in the singer.io fork of tap-mssql. It did require being enabled by a DBA at the database level and also at the table level. I'm not sure if that is the same mentioned here in the article but you might scan that repo also to see how it was implemented - if it's the same thing. cc @John Timeus (Slalom Consulting)

Yeah the log based tooling that the tap we are using is based on the SQL Server "Change Tracking" feature, which is similar but lighter performance hit on the source DB at the expense of details. It doesn't capture before and after values like CDC, just which PKs in a table have a change since an input version number

Curious! Thanks for the responses

@visch, as a fyi I'm working on adding CDC rather than Change Tracking which is what is what the singer.io mssql tap is using. My project to enhance the pipelinewise is mostly done now is located here : https://github.com/s7clarke10/pipelinewise-tap-mssql

awesome!