Updated January 13, 2024
Learn how to manage your connector schemas in your Fivetran dashboard.
Each connector profile includes a Schema tab, which displays information about your connector's schemas. Learn more about schemas in our core concepts documentation.
The Schema tab looks different depending on which connector you view. Depending on your connector, you'll see one of the following:
- A fully customizable schema
- A semi-customizable schema
- A non-customizable schema
- (Magic folder connectors only) A list of source files and their corresponding destination tables. The list indicates if any source files are in an unsupported format.
The Schema tab contains information about the following:
Types of schemaslink
There are several different types of schemas:
- Source schema: A source schema shows how your data is structured in your data source. For Application sources, this is generated by Fivetran.
- Connector schema configuration (also called "connector schema"): A connector schema configuration defines the data that Fivetran will sync to your destination. Depending on your connector, you can customize your configuration by excluding tables, blocking columns, or hashing columns. View your connector schema configuration on the Schema tab.
- Destination schema: A destination schema defines how your data is structured in your destination. Fivetran typically creates one destination schema per connector, though we can create multiple destination schemas for database sources. Learn more in our destination schema and table management documentation.
We automatically perpetuate changes in the source schema to the connector schema configuration and destination schema to ensure that we accurately sync your data. Read our schema migrations documentation to learn more.
We also update your destination schema when you update your connector configuration schema. For example, if you hash column
field, we will sync hashed data to the
field column in your destination, then ask you to choose whether we re-sync that table to overwrite the existing unhashed data or if we just sync hashed data moving forward. Depending on your connector type, we may automatically trigger a re-sync if you include a table in your connector schema configuration that had been previously excluded from syncs. Learn more in our database automatic re-sync documentation.
When you change a column's data type in your source, we update the data type in the corresponding destination column. Learn how in our changing data type documentation.
The tab displays a list of your connector's schemas with their constituent tables and columns listed below them. Both active and inactive schemas are listed. Click the black arrow to the left of the schema name to collapse or expand the schemas.
If your connector has more than one schema, a schema navigation menu appears on the right side of the screen. Use it to quickly find your schemas in a long list.
To reload your schema, click Reload schema.
To collapse your schemas, click Collapse all.
To expand your schemas, click Expand all.
NOTE: The Schema tab of a Magic Folder connector has a different view. Learn more in our Files Schema documentation.
Blocking a schema prevents Fivetran from syncing any table or column within that schema.
To block a schema, set the toggle next to the schema name to OFF, then click Save changes.
If you want to un-block this schema in the future, set the toggle back to ON. Depending on how long you wait and your connector type, you may need to do a historical re-sync to update that schema's data in your destination, which increases your MAR.
Define Schema Change Handling settingslink
To view or change your Schema Change Handling settings, click the gear icon above the schema list.
A drop-down menu appears. Choose from the following Schema Change Handling options:
- Allow all. New schemas, tables, and new columns for existing tables are synced into the destination.
- Allow columns. Only new columns for existing tables are synced into the destination. New schemas and configurable tables* are blocked from being synced to the destination.
- Block all. New schemas, configurable tables*, and new columns for existing tables are not synced into the destination.
*NOTE: In some connectors with a defined schema, including many of our application connectors, some tables are not configurable. Non-configurable tables cannot be completely blocked. If you select the Block All option, we only sync the primary keys of the non-configurable tables.
If you want to receive a notification email whenever we detect new schemas, tables, or columns in the source, check the Send notifications box.
NOTE: We do not send notification emails for deletions in the source.
If you switch to a different setting, click Save changes to save your new setting.
To find a specific table, search for it by name using the search bar.
To find all active tables, click the filter icon and select Only show selected tables.
By default, all tables in a selected schema are automatically selected to be synced. However, you can choose to block certain tables from syncing.
To block a table, click the checkbox next to the table name, then click Save changes. You can block multiple tables at once.
If you want to un-block this table in the future, click the checkbox. Depending on how long you wait and your connector type, you may need to do a historical table re-sync to update that table's data in your destination, which increases your MAR.
View or change sync modelink
If your connector supports history mode, you can view and change your tables' sync mode. Hover over the table's row to see its current sync mode. If the table currently uses history mode, history is displayed in the table's row even if you are not hovering over it.
TIP: See which connectors support history mode in our History mode connector list.
To change the table's sync mode, click on the mode name to open a drop-down menu. Choose the sync mode that best suits your purposes:
- Soft delete mode (enabled by default): Source record changes are reflected in the destination. In this mode, source deletes are marked as deleted and stay in the destination.
- History mode: Source record changes and deletes are recorded and timestamped as new records in the destination, resulting in more monthly active rows and higher cost.
To save the settings after you switch the sync mode, click Save changes.
To re-sync a table, hover over the table's row in the schema list. Click the Resync button that appears.
You can only re-sync active tables.
Block a columnlink
By default, all columns in a selected table are automatically selected to be synced. Primary key columns cannot be blocked.
If you want to block certain columns, click the checkbox next to the column name, then click Save changes. You can block multiple columns at once.
Hash a columnlink
If your connector supports column hashing, you can hover over the column's name to see its hash mode (hashed or unhashed). Primary key columns cannot be hashed.
TIP: See which connectors support column hashing in our column hashing connector list.
To change this column's hash mode, click on the mode name to open a drop-down menu. Choose one of the following settings:
- Unhashed (enabled by default): Data values at the source will be replicated identically to the destination.
- Hashed: Hash data values in this column before syncing data to your destination.
If you switch to a different mode, click Save changes to save your new mode. You can change the hash mode for multiple columns at once.