Release Notes

November 2024

We now support IAM role authentication to authorize S3 buckets associated with Snowflake destinations configured for the Hybrid Deployment model.

September 2024

We now support Snowflake's internal stage to temporarily store data before writing it to Snowflake destinations configured for the Hybrid Deployment model.

January 2023

We have added a new destination setup test to verify if the default role assigned to the Fivetran user account has the required permissions on the storage integration. We perform this test only if your Snowflake destination is hosted on Google Cloud Platform (GCP).

December 2022

We now set base64 as the default BINARY input format for the Snowflake destination.

September 2022

Azure Private Link is now generally available for Snowflake.

For more information, see our Snowflake setup guide.

August 2022

We have added support for the XML data type. We convert XML data type to VARIANT data type in your Snowflake destination. You can now use XML functions on the VARIANT data type columns to extract and process XML data.

We consider XML as the subtype of JSON. If we receive a JSON value in an XML column from the source, we write the data as VARIANT in your Snowflake destination. We then convert all the existing XML values to JSON strings. To extract the values, you must use the PARSE_XML function on the XML data.

For example, if we receive the following XML value from the source, <root></root>, we process and store the data in Snowflake as <root></root>. When we convert the value to JSON, the value looks like XML in string format, "\n<root></root>".

However, if we receive any other data type value for the same column from the source, we store the data as TEXT in your Snowflake destination.

March 2022

You no longer need to include the word "fivetran" in your Snowflake username.

January 2022

AWS PrivateLink is now generally available for Snowflake.

For more information, see our Snowflake setup guide.

September 2021

You can now stage your data in Google Cloud Storage (GCS) if your Snowflake destination is deployed on Google Cloud Platform (GCP) for improved performance. Grant the FIVETRAN_ROLE the CREATE INTEGRATION permission using the following query:

GRANT CREATE INTEGRATION ON ACCOUNT TO ROLE FIVETRAN_ROLE;

You can now use PrivateLink as a connection method for the following destinations:

• Redshift
• Snowflake

This feature is in BETA and available only for Business Critical accounts.

July 2021

You can now use the following encryption algorithms for Key-pair authentication:

• AES128
• AES256
• DES3

June 2021

You can now customize the credentials that Fivetran uses to access your Snowflake destination to run dbt jobs. Add your credentials in the Credentials section of your dbt Tranformations setup form. Learn more in our dbt setup guide.

February 2021

We have added a new optional field Role to the Snowflake destination setup form. If you want Fivetran to use a role other than your default role, enter the role’s name during the destination setup in the Role field. See our setup instructions for more information.

September 2020

We have added a new test in the Snowflake destination setup form to verify CREATE SCHEMA and CREATE TEMPORARY TABLES permissions. When you set up your Snowflake destination, the new test will automatically validate these permissions.

July 2020

We have reduced the sync duration of append-only tables. During internal performance testing, we observed a reduction in sync time for destinations with large table sizes. We are gradually rolling out this change to all our existing destinations.

June 2020

We now replicate empty tables in a PostgreSQL source database as empty tables in the destination.

We have expanded the current public API endpoint Create a Destination. Now, you can:

• control whether setup test are executed automatically by specifying the run_setup_tests parameter.
• create a Snowflake destination with password-based or key-based authentication types. Read our updated documentation about Snowflake destination config.

February 2020

We now support key pair authentication to connect to your Snowflake destination.

November 2019

We now support Snowflake on Google Cloud Platform. For more information, see Snowflake's website.

October 2019

Snowflake does not allow the following ANSI reserved keywords to be column names when they are capitalized:

• CONSTRAINT
• CURRENT_DATE
• CURRENT_TIME
• CURRENT_TIMESTAMP
• CURRENT_USER
• LOCALTIME
• LOCALTIMESTAMP

To ensure a valid column name, Fivetran converts the keyword to lowercase and encases it in double quotes (for example, LOCALTIME becomes "localtime"). When you query these columns, be sure to use the converted column name.

March 2019

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 destinations before April 30. Not doing so will result in a connection failure.

Databases:

• MariaDB
• MongoDB
• MySQL
• Oracle
• PostgreSQL
• SQL Server

Destinations:

• Redshift
• Azure Synapse
• Snowflake

If you don't use any of the above databases or destinations with Fivetran, you don't need to take any action.

August 2018

For Oracle connectors, TIMESTAMP data types will now be represented as TIMESTAMP WITHOUT TIME ZONE types in the destination. Since DATE column types are also timezone unaware, dates that lack a time component will be interpreted as TIMESTAMP WITHOUT TIME ZONE types as well. This update is currently only available for Snowflake destinations.