*Is this your first time deploying Airbyte*: Yes *...
# troubleshooting
h
Is this your first time deploying Airbyte: Yes OS Version / Instance: Ubuntu 20.04.4 LTS on Azure Memory / Disk: 4vcpu, 16GB ram, 30GB disk Deployment: Docker-compose Airbyte Version: 0.35.35-alpha Source name/version: MSSQL / 0.3.17 Destination name/version: csv on blob / 0.1.3 Description: When the incremental sync seems to be complete, the source seems to hang for 5 minutes. Then the database pool is closed, and the sync process fails. The record count keeps increasing on every sync, so it’s not a single record causing the problem, and it seems like the sync is actually complete - the source just doesn’t realise it yet.
With a full sync everything just works (it just takes a long time), it’s only the incremental sync that fail
h
It is full refresh with overwrite mode, still it is stuck.
a
Hi @Huib, incremental sync consume records with a query like
SELECT * FROM your_table WHERE your_cursor_field > last_cursor_value_in_airbyte_state
. Maybe there's something to investigate on the cursor field type / value. We're moving our community support on Discourse soon, do you mind posting on the Troubleshooting forum if you'd like to follow up on this topic with our team?
h
@[DEPRECATED] Augustin Lafanechere what kind of things should i look at? The only thing I can think of is seeing what query is being run by airbyte, and re-running that using a different mechanism (data studio, python, etc). The database is an Azure hosted db, and the server-side logs are surprisingly, ehm, unhelpful. I’ll post on discourse too, thanks!
Ok, yes, that was actually really helpful. The query is slow (the table is large-ish, and it seems there’s no index on the date field I’m using for the filter) and returns recent data relatively quickly, then hangs scanning the entire table for more records (which don’t exist). This probably causes a timeout somewhere.