Release Noteslink
February 2024link
We can now sync primary key-less tables using Fivetran Teleport Sync.
February 2021link
We can now sync tables that do not have all of their columns included in their CDC instances. For these tables, we only sync the columns that are present in the CDC instance. To include excluded columns, delete your old CDC instance and create a new one that includes all columns.
September 2020link
We have optimized the queries that we use to retrieve table and column metadata from your database during our data syncs. Our new queries improve your sync speed, especially if you have large schemas.
June 2020link
We have changed our sync strategy for users who chose to exclude new tables from their data syncs by default. Our new sync method improves your sync speed, especially if you have a large number of tables.
April 2020link
We now add a _fivetran_synced
column while syncing empty tables and columns from the source.
March 2020link
Fivetran has released an updated version of our SQL Server connector, which offers improved sync reliability. We will add a number of upgrades to this version in the coming weeks:
We will support Change Data Capture as an incremental update mechanism for all customers.
We will support the following data types:
- BINARY
- VARBINARY
- IMAGE
- ROWVERSION
- TIMESTAMP
- GEOMETRY
- GEOGRAPHY
For more information, see our SQL Server documentation.
January 2020link
We now support Change Data Capture as an incremental update mechanism. To learn more, see our SQL Server setup guides.
December 2019link
Our SQL Server connector can now sync empty tables. You do not need to take any action to leverage this improvement. All the empty tables you previously selected to sync will now sync.
September 2019link
If you have a logging service connected to your Fivetran account, the import progress of your tables in the event logs will be visible in your logs as an import_progress
event. Table names will be in either the COMPLETE
or IN_PROGRESS
state, depending on their sync status. Tables that are not reported in the event have not started their import.
March 2019link
Fivetran has added core support for a TIMESTAMP WITHOUT TIMEZONE type. Up until now, Fivetran assumed that timestamps without timezone were in UTC. This addition means databases with a TIMESTAMP WITHOUT TIMEZONE type - MySQL, Oracle, PostgreSQL, SQL Server - will replicate to a more correct destination type. TIMESTAMP WITHOUT TIMEZONE support is immediately available for Oracle, PostgreSQL, and SQL Server. MySQL / MariaDB support will be released soon.
Source | Applicable Type |
---|---|
Oracle | TIMESTAMP |
PostgreSQL | TIMESTAMP |
SQL Server | DATETIME, DATETIME2, SMALLDATETIME |
MySQL / MariaDB | DATETIME |
This change is backwards compatible. Fivetran's core will continue assuming UTC time zone if the destination type is TIMESTAMP WITH TIMEZONE. In order to get the more specific type, drop the table in the destination and re-sync the table in your Fivetran dashboard.
We are changing our architecture to allow for much higher data throughput. Starting on April 30, 2019, all Fivetran connectors will originate from a new set of fixed IP addresses. For the US region, these IPs are:
- 35.227.135.0/29
- 35.234.176.144/29
- 52.0.2.4/32.
Update your IP safelists for the following databases and warehouses before April 30. Not doing so will result in a connection failure.
Databases:
- MariaDB
- MongoDB
- MySQL
- Oracle
- PostgreSQL
- SQL Server
Warehouses:
- Redshift
- Azure Synapse
- Snowflake
If you don't use any of the above databases or warehouses with Fivetran, you don't need to take any action.
February 2019link
Tables with clustered indices are now queried using smaller page sizes. This reduces the contiguous length of time that a Fivetran connector has a lock on a table from which it's reading, without adversely affecting sync speeds.
November 2018link
You can now trigger re-syncs of individual tables from your Fivetran dashboard:
The re-sync button appears when you hover your cursor over the row that contains the table name.
This feature is available for the following connectors:
- DynamoDB
- MongoDB
- MySQL
- NetSuite SuiteAnalytics
- Oracle
- PostgreSQL
- Salesforce
- SQL Server
- Zuora
October 2018link
For the following warehouses, Fivetran now drops the primary_key
field from existing tables in your warehouse if there is a primary_key
coming in from your data source:
- MySQL
- PostgreSQL
- SQL Server
- Redshift
May 2018link
We can now sync columns with the data type DATETIMEOFFSET
. The values are converted to UTC using the timezone information present in the data.