Connector Improvement: Set Log Sequence Number within Connector
Answered
Currently if a database migration or side by side database upgrade is performed the options are to either:
1. Perform a historical resync - large cost against MAR for large databases
2. Support request - pause connector, open a support request, scheduling time for configuration update to have log sequence configured behind the scenes and then unpause the connector
3. Create a new connector - breaks any naming convention dependencies
It would be helpful for this to be more self service as many times database migrations are performed late at night / early morning where it can be difficult to schedule a support resource from Fivetran to participate in the upgrade.
Ask would be to be able to set the starting log sequence number for a database as part of each connector. This can be performed already by other similar services such as AWS DMS, Azure Database Replication, Debezium, GCP Database Migration Service
-
Official comment
Hi David,
Thanks for your request. This is among one of the most commonly requested capabilities for our database connectors. Many database operations that are extremely common, such as upgrade, failover, migration should not be impacting the Fivetran connectors (ideally).
This is a capability I am hoping we can build soon, but do not have a timeframe for at the moment. If you could share any other details on other operations that cause these re-syncs, please share them here so I can bring this discussion to our teams.
Please sign in to leave a comment.
Comments
1 comment