March 2022link
You no longer need to include the word “fivetran” in your Snowflake username.
January 2022link
AWS PrivateLink is now generally available for Snowflake.
For more information, see our Snowflake setup guide.
September 2021link
You can now stage your data in Google Cloud Storage (GCS) if your Snowflake data warehouse 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:
This feature is in BETA and available only for Business Critical accounts.
July 2021link
You can now use the following encryption algorithms for Key-pair authentication:
- AES128
- AES256
- DES3
February 2021link
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 2020link
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 2020link
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 customers.
February 2020link
We now support key pair authentication to connect to your Snowflake warehouse.
November 2019link
We now support Snowflake on Google Cloud Platform. For more information, see Snowflake’s website.
October 2019link
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.