After you initially connect an integration, Stitch will perform a structure sync to detect the databases, tables, and columns in the integration.

Once the structure sync is complete, you’ll be able to select the individual tables and columns you want to sync. Stitch calls this whitelisting and it’s currently available only for certain integrations, which you can read more about below.

These integrations require tables and columns to be selected before data can begin replicating. Once the setup process is complete, Stitch will begin replicating your data.


Integrations that Support Whitelisting

The following integrations support some level of whitelisting:

Integration
Databases
Tables
Columns
Database Integrations
MongoDB
Autopilot
Facebook Ads
Google Adwords
HubSpot
Mixpanel
NetSuite
Salesforce
Zuora

Keep in mind that:

  • Only these integrations support whitelisting. If an integration doesn’t support whitelisting, all available data - meaning all the tables and columns that Stitch can access - will be set to sync.

    For detailed info on the data Stitch syncs from SaaS integrations, check out the Schema section of any integration’s guide.

  • Only the tables and columns you set to sync in these integrations will be replicated. If nothing is set to sync in these integrations, the integration will have a status of Not Configured. Replication won’t begin until some objects are synced.


Selecting Data to Sync

Selecting data to sync is easy. All you need to do is click into the integration from the Stitch Dashboard page and find the object you want to sync. Then, click the checkbox next to the object’s name. A green checkmark means the object is set to sync.

By default, all columns in a table will be set to sync. For integrations that support whitelisting, you can un-sync columns by clicking on the table name and then selecting columns to un-sync.

Additionally, if you’re syncing data from a database integration, you’ll be prompted to select a Replication Method for tables that you set to sync.

Parent Objects & Syncing

The table containing these columns is not set to sync. Please sync the parent table to ensure replication of columns selected on this screen.

If you see this message or something similar on the Integration Details page, it means that the object above what you’re looking at - in this case, a table - isn’t set to sync.

Parent objects must set to sync for the objects under them to successfully replicate. To be clear: for a column to sync, the table above it must also be set to sync. If applicable, so must the schema containing the table, and the database containing the schema.

Syncing Database Views

While the steps for syncing a database view are almost the same as those for syncing a table, there are some slight differences.

For more info check out the Syncing Database Views guide.

Syncing New & Additional Columns on Already-Syncing Tables

What happens when you’ve added a brand-new column in the data source or you want to sync additional columns on an already-syncing table?

For more info check out the Syncing New & Additional Columns guide.


Unsyncing Data

There a few ways you can unsync objects:

  1. Unsync All. To unsync all objects in the page you’re currently on, click the grey checkbox next to the Table/Column Name column, then click Stop Syncing All.

    Note that if this is a parent object - meaning it contains an object beneath it - Stitch will also stop syncing the child object.

  2. Unsync individual objects. Locate the object and click the checkbox next to the object’s name.

Whatever method you choose, the checkbox(es) of the object(s) you unsync will turn grey and the Method will change to Not Synced.

Additionally, if you want to re-sync a previously unsynced table, you’ll need to set the table’s Replication Method again.


Troubleshooting

Missing Objects

Stitch cannot detect any objects (databases, tables, etc.) at or below this level.

If you receive this message or you can’t find an object (database, table, column, etc.), it’s typically a permissions issue.

Not Supported Table/Column Messages in Database Integrations

If you see a status of Not Supported for a table or column in a database integration, there a few potential root causes:

  • Insufficent permissions. Verify that the Stitch user has all the required permissions as outlined in the Setup instructions for the database. Docs for database integrations can be found here.

    After you grant the required permissions and a full replication cycle has completed, the table’s Sync Status should change to Supported and be available for syncing.

  • Unsupported column. If a column is displayed as Not Supported, it may be that the column contains an unsupported data type.
  • Unsupported table type. If it’s a MySQL integration, it may be that the table is a type that Stitch doesn’t currently support. Currently only InnoDB tables are supported. If it’s another type - such as MyISAM - you’ll have to convert the table to InnoDB format to sync it through Stitch.

    Performing the conversion requires tech expertise and familiarity with MySQL, so we recommend looping in a database admin or another member of your tech team to help out.

    After you successfully convert the table to InnoDB format and a full replication cycle has completed, the table’s Sync Status should change to Supported and be available for syncing.

Parent Object Isn’t Set to Sync

The table containing these columns is not set to sync. Please sync the parent table to ensure replication of columns selected on this screen.

If you see this message or something similar on the Integration Details page, it means that the object above what you’re looking at - in this case, a table - isn’t set to sync.

Parent objects must set to sync for the objects under them to successfully replicate. To be clear: for a column to sync, the table above it must also be set to sync. If applicable, so must the schema containing the table, and the database containing the schema.



Questions? Feedback?

Did this article help? If you have questions or feedback, please reach out to us.

Tags: replication