SQL Server big table to S3 fails

Hello everyone!

We are facing an issue when we try to ingest a big Sql Server (Incremental | Append) to S3.

I’m a beginner with Airbyte and I’m trying to test Airbyte at the company where I work, using the SQL Server as a source and AWS S3 as the destination.

Airbyte is Helm at version 0.40.14 and all dependencies are at version 0.40.10
Source: SQL Server - 0.4.23
Destination: S3 - 0.3.16

We are facing a problem when we are trying to transfer data from big tables, exceeding more than 100 million rows. The routine responsible for this transfer usually takes days to process and it´s very common to fail. When it happens, the engine does not continue from the step where the error happened not obeying the last field cursor recorded on S3. Due to, some record duplications may occur.
In order to solve this problem, we’ve already tested several versions available, but unfortunately, this problem still persists.

I do appreciate any help you can provide.
Best regards,

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
The Community Assistance Team