Connector Improvement: Functionality to force the table to do a teleport sync even if timetravel is possible
We have a use case where we have a source owned by a vendor. We are sync-ing some tables that are being truncated and reloaded every batch run.
The source database is snowflake. Change tracking is turned on for those tables.
During our sync, fivetran does a timetravel sync on such tables. We get a full delete on all records and a new set of records for every batch run.
These tables are relatively small and a switch to teleport sync is not a big hit on performance.
It would be good to be able to force a table to do teleport syncs only so that we do not have a huge number of inactive records on our destination table.
Please sign in to leave a comment.
Comments
0 comments