After you initially connect a database integration to Stitch, we'll perform a structure sync to detect the schemas, tables, and columns in your database. Once this sync is complete, you'll be able to to select the data you want to sync, set table Replication Methods, and choose a Replication Frequency for the integration.
Your data will begin replicating as soon as you complete the setup process.
In this article, we'll cover:
Missing & Unsupported Databases/Tables
If you're missing databases and/or tables, verify that you gave the Stitch user all the required permissions. Only the databases and tables that our user has access to will display in the Stitch app for syncing.
If a table has a Sync Status of
Unsupported, try these troubleshooting tips.
Database integrations give you the ability to sync down to the columnar level.
Here's a look at syncing a new table and assigning a replication method:
You can unsync databases, tables, and/or columns, individually or en masse with just a few clicks.
Unsyncing individual databases, tables, and columns is done exactly the opposite of syncing.
You can unsync all databases, tables, and/or columns by clicking the grey icon above the Syncing Icon column and selecting Stop Syncing All:
You can also click into the database/table and then click the Stop Syncing button located above the schema section.
Note: if you want to resync a previously unsynced table, you'll need to set the table's replication method again.
A few factors can play into how quickly you'll see the new data or changes take effect in your data warehouse. The volume of data in your tables, the replication method, and the integration's replication frequency setting can all impact how long it takes for your data to replicate.
If your data hasn't shown up after a reasonable amount of time, please reach out to our support team. We'll help you get to the bottom of it.
We recommend that you check out the articles linked below in the Related section. These resources will help you understand how your data will appear in your data warehouse, how Redshift handles schema changes, why some tables/columns have hashed names, and more.