Summary
The MSSQL connector in Airbyte is checking for the initial snapshot LSN even during incremental syncs, causing the ‘savedOffsetStillPresentOnServer’ function to eventually fail. This results in the error message ‘Saved offset no longer present on the server. Please reset the connection, and then increase binlog retention and/or increase sync frequency’. There is a detailed description of the problem on a Github issue.
Question
hey guys, i am having an issue with the mssql connector. Airbyte is checking for the initial snapshot lsn, even when running incremental syncs. This means that the function “savedOffsetStillPresentOnServer” will fail eventually and return “Saved offset no longer present on the server. Please reset the connection, and then increase binlog retention and/or increase sync frequency”
There is an issue on Github that describes the problem in more detail, but i dont know how to get the developers involved, i dont know any java sadly.
https://github.com/airbytehq/airbyte/discussions/40726
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.