Connector Improvement: Truncating a partition of a partitioned table on the sql server source should not trigger a full sync
Answered
Truncating a partition of a partitioned table on the sql server source should not trigger a full sync of the connector. This causes delays in data syncs and delivering data on the target in a timely manner. This feature becomes very critical considering we don't want too be syncing tables for weeks when all we did was truncate a partition of a partitioned table at source based on data retention policies. Not having this feature is glaring when the tables are large.
-
Official comment
Hi Ram,
Thank you for sharing this feedback, and I’m really sorry for the disruption you've experienced as a result of this behavior. I completely understand how frustrating and costly it can be especially when managing large tables where only a partition was truncated.
We are looking into this scenario. While I don’t have a timeline to share at the moment, addressing unnecessary full syncs in partitioned truncation cases is something we’ve acknowledged internally and have added to our backlog.
Thank you again for sharing your feedback with us!
- Rean Rodrigues
Product Manager Databases -
Any updates on this one? This will help meet our SLAs, currently we are forced to stagger truncating our partitions on tables at source due to this resync issue.
Please sign in to leave a comment.
Comments
2 comments