Hello Guys, i been following airbyte for a long time now, and it sure has walked a long mile from my last attempt to use the tool; i have an azure deployment where i am running Airbyte as suggested in the documentation; on a 16vCPU 64GB machine My attempt is to sync 2 MSSQL databases ; the sync itself is working like a charm, i have it set for dedup+history which is my current need as the tables can be updated but they are too big for a full refresh ; but ; and there is always a but, its bothering me the amount of time it takes , In the log summary it says 1.300 lines were sync but it took over 1 hour to do it . Is this an expected behaviour? Am i doing something wrong or there is something i should be paying attention to and i am not? neither of the databases seems to be on any sort of stress , but the normalization phase is taking ages to complete. Any help is appreciated and thanks again for the awesome tool you guys are working on

@[DEPRECATED] Marcos Marx turned this message into Zendesk ticket 2998 to ensure timely resolution!

Hi! Glad you're enjoying Airbyte and that everything is working :) in making connectors more stable with recent updates, some connectors may have slowed down. One solution is to allocate more memory: https://docs.airbyte.com/operator-guides/scaling-airbyte/#memory https://docs.airbyte.com/operator-guides/configuring-connector-resources/#configuring-connection-specific-requirements Could you provide your logs? I'd like to see how fast the connection is. If it's syncing 2-3K rows per second that's the norm.

hello Nataly thanks a lot for the reply ; what i see in the interface is this : its taking over 1 hour to sync 1.5k rows ; and all the time is spent on the create incremental model phase

I see, that's definitely out of the norm. What version of Airbyte and MSSQL connectors are you using? Can you please provide the full logs?

Hi Nataly , both connectors are marked as Lastest • Airbyte is 0.40.15 • Source MSSQL 0.4.22 • Destination MSSQL 0.1.20 attached the last run i made which took 2 hours

Thanks for the logs! Let me ask for some input from my team and I'll get back to you!