Switching database host for connection

Slack Knowledge Base Q&A Connector Questions
, , , ,
1

Summary

When switching the database host for a connection, it is important to consider potential impacts on stream states and data synchronization.


Question

Hello Airbytians! I have had a connection to a prod DB running for about a year now (mostly incremental but some full refreshes) and now I have a read replica that I want to switch the db host to. I dont anticipate issues but is there anything to know prior to doing this? Will our stream states wipe if we update the source to pull from the replica db?


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["switching-database-host", "connection", "stream-states", "data-synchronization", "replica-db"]
2

Generally updates to the source won’t mess up anything with the current state. If you want peace of mind, you can always take a backup of the state object from the UI or database before making the change (or just make sure you have a DB backup in general).

We’ve swapped endpoints, sources, etc. and everything is generally fine as long as you don’t actually recreate it. The only exception is destructive options like “delete my data” or a running a Reset on a stream, which will clear the state.