Hello! We are experimenting with a Kubernetes deployment of Airbyte 2.0.1 as a possible replacement for Fivetran. However, we're encountering challenges with CDC-mode syncs for SQL Server. Specifically, for recent versions (4.3.x) of the SQL Server connector, we're encountering this issue. We downgraded the connector to 4.2.6 per the suggested work-around on that issue, but then receive a different runtime error (

java.nio.file.NoSuchFileException: /tmp/cdc-db-history18445439749573321969/dbhistory.dat

). Is there a version of Airbyte that is known to work with the SQL Server connector in CDC mode?

The knowledge sources do not contain enough information to give you a definitive answer about which specific Airbyte platform version (e.g., 2.0.1) is known to work reliably with the SQL Server connector in CDC mode, nor do they address the

NoSuchFileException: dbhistory.dat

error you're seeing with 4.2.6. What the knowledge sources do confirm about the 4.3.x connector issues: • Issue #73326 ("Could not find existing redo log information while attempting schema only recovery snapshot") affects versions 4.3.2, 4.3.3, 4.3.4, and 4.3.5, and is still open. [source-mssql issue 73326] • The suggested workaround — running a full initial load on 4.2.6 first, then upgrading to 4.3.x for incremental CDC — is acknowledged but noted to potentially cause data gaps and is not ideal. [source-mssql issue 73326] • A separate regression in 4.3.x also causes malformed JDBC timeout strings (

The timeout 300;socketTimeout=0;cancelQueryTimeout=0 is not valid

), with 4.2.6 cited as the last known-good version for that specific bug. [syncs fail invalid timeout] • Another regression in 4.3.4 breaks CDC on Azure SQL geo-replicas due to LSN validation changes. [LSN validation regression] The

NoSuchFileException: dbhistory.dat

error you're hitting on 4.2.6 is not covered in the knowledge sources I have access to. Recommended next steps: 1. Open a support ticket or GitHub issue for the

dbhistory.dat

error specifically — it's not documented in the sources available here. 2. Monitor the open issue #73326 for an official fix, as it has been escalated to the Airbyte engineering team. 3. Join the Airbyte Community Slack where other users may have encountered and resolved the same combination of issues. I'm sorry I can't give you a more definitive version recommendation — the knowledge sources simply don't contain that information. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.