[PostgreSQL / SQL Server sources] Change Data Capture (CDC) implementation questions #52058
Unanswered
kev-datams
asked this question in
Connector Questions
Replies: 1 comment
-
Hello @marcosmarxm, discussion created as discussed, please could you tag people who may help ? 🙏 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Airbyte team,
We consider using
CDC
to retrieve data from bothPostgreSQL
andSQLServer
sources (with 3 days of log retention).FULL SYNC
, our main goal is to absolutely minimize the impact on production DB instances (CPU, RAM, locks, tempdb size, etc).💡 As we have some huge tables to sync, we count on the Airbyte
resumable full refresh
capability to be able to:❓ Regarding this feature, we have some questions:
PostgreSQL
andSQLServer
?resumable full refresh
concretely operates (technical mechanisms / cursor usage / snapshot isolation / temp disk flush / ...) on:PostgreSQL
?SQLServer
?considering a first sync lasting a long time (eg: 48 hours), what are the risks on production DB instances ? (CPU, RAM, locks, tempdb size, ...)
we observed the
LSN commit behaviour
parameter onPostgreSQL
connector:While reading data
value will:SQLServer
, does it mean it is:While reading data
behavior ? (if so, how ?)After loading data in the destination
behavior ? (if so, how ?)I guess above questions are common to many people wishing to synchronize large volumes of data, and the answers might be of great interest to them ! 🙏
Thanks a lot for clarifications 🔥
Beta Was this translation helpful? Give feedback.
All reactions