Skip to main content

Snowflake

Overview

The Snowflake source allows you to sync data from Snowflake. It supports both Full Refresh and Incremental syncs. You can choose if this connector will copy only the new or updated data, or all rows in the tables and columns you set up for replication, every time a sync is run.

This Snowflake source connector is built on top of the source-jdbc code base and is configured to rely on JDBC 3.14.1 Snowflake driver as described in Snowflake documentation.

Resulting schema

The Snowflake source does not alter the schema present in your warehouse. Depending on the destination connected to this source, however, the result schema may be altered. See the destination's documentation for more details.

Features

FeatureSupported?(Yes/No)Notes
Full Refresh SyncYes
Incremental - Append SyncYes
NamespacesYes

Getting started

Requirements

  1. You'll need the following information to configure the Snowflake source:
  2. Host
  3. Role
  4. Warehouse
  5. Database
  6. Schema
  7. Username
  8. Password
  9. JDBC URL Params (Optional)
  10. Create a dedicated read-only Airbyte user and role with access to all schemas needed for replication.

Setup guide

1. Additional information about Snowflake connection parameters could be found here.

This step is optional but highly recommended to allow for better permission control and auditing. Alternatively, you can use Airbyte with an existing user in your database.

To create a dedicated database user, run the following commands against your database:

-- set variables (these need to be uppercase)
SET AIRBYTE_ROLE = 'AIRBYTE_ROLE';
SET AIRBYTE_USERNAME = 'AIRBYTE_USER';

-- set user password
SET AIRBYTE_PASSWORD = '-password-';

BEGIN;

-- create Airbyte role
CREATE ROLE IF NOT EXISTS $AIRBYTE_ROLE;

-- create Airbyte user
CREATE USER IF NOT EXISTS $AIRBYTE_USERNAME
PASSWORD = $AIRBYTE_PASSWORD
DEFAULT_ROLE = $AIRBYTE_ROLE
DEFAULT_WAREHOUSE= $AIRBYTE_WAREHOUSE;

-- grant Airbyte schema access
GRANT OWNERSHIP ON SCHEMA $AIRBYTE_SCHEMA TO ROLE $AIRBYTE_ROLE;

COMMIT;

You can limit this grant down to specific schemas instead of the whole database. Note that to replicate data from multiple Snowflake databases, you can re-run the command above to grant access to all the relevant schemas, but you'll need to set up multiple sources connecting to the same db on multiple schemas.

Your database user should now be ready for use with Airbyte.

Authentication

Login and Password

FieldDescription
HostThe host domain of the snowflake instance (must include the account, region, cloud environment, and end with snowflakecomputing.com). Example: accountname.us-east-2.aws.snowflakecomputing.com
RoleThe role you created in Step 1 for Airbyte to access Snowflake. Example: AIRBYTE_ROLE
WarehouseThe warehouse you created in Step 1 for Airbyte to sync data into. Example: AIRBYTE_WAREHOUSE
DatabaseThe database you created in Step 1 for Airbyte to sync data into. Example: AIRBYTE_DATABASE
SchemaThe schema whose tables this replication is targeting. If no schema is specified, all tables with permission will be presented regardless of their schema.
UsernameThe username you created in Step 2 to allow Airbyte to access the database. Example: AIRBYTE_USER
PasswordThe password associated with the username.
JDBC URL Params (Optional)Additional properties to pass to the JDBC URL string when connecting to the database formatted as key=value pairs separated by the symbol &. Example: key1=value1&key2=value2&key3=value3

Network policies

By default, Snowflake allows users to connect to the service from any computer or device IP address. A security administrator (i.e. users with the SECURITYADMIN role) or higher can create a network policy to allow or deny access to a single IP address or a list of addresses.

If you have any issues connecting with Airbyte Cloud please make sure that the list of IP addresses is on the allowed list

To determine whether a network policy is set on your account or for a specific user, execute the SHOW PARAMETERS command.

Account

SHOW PARAMETERS LIKE 'network_policy' IN ACCOUNT;

User

SHOW PARAMETERS LIKE 'network_policy' IN USER <username>;

To read more please check official Snowflake documentation

Changelog

Expand to review
VersionDatePull RequestSubject
0.3.22024-02-1338317Hide oAuth option from connector
0.3.12024-02-1335220Adopt CDK 0.20.4
0.3.12024-01-2434453bump CDK version
0.3.02023-12-1833484Remove LEGACY state
0.2.22023-10-2031613Fixed handling of TIMESTAMP_TZ columns. upgrade
0.2.12023-10-1131252Snowflake JDBC version upgrade
0.2.02023-06-2627737License Update: Elv2
0.1.362023-06-2027212Fix silent exception swallowing in StreamingJdbcDatabase
0.1.352023-06-1427335Remove noisy debug logs
0.1.342023-03-3024693Fix failure with TIMESTAMP_WITH_TIMEZONE column being used as cursor
0.1.332023-03-2924667Fix bug which wont allow TIMESTAMP_WITH_TIMEZONE column to be used as a cursor
0.1.322023-03-2220760Removed redundant date-time datatypes formatting
0.1.312023-03-0623455For network isolation, source connector accepts a list of hosts it is allowed to connect to
0.1.302023-02-2122358Improved handling of big integer cursor type values.
0.1.292022-12-1420436Consolidate date/time values mapping for JDBC sources.
0.1.282023-01-0620465Improve the schema config field to only discover tables from the specified scehma and make the field optional
0.1.272022-12-1420407Fix an issue with integer values converted to floats during replication
0.1.262022-11-1019314Set application id in JDBC URL params based on OSS/Cloud environment
0.1.252022-11-1015535Update incremental query to avoid data missing when new data is inserted at the same time as a sync starts under non-CDC incremental mode
0.1.242022-09-2617144Fixed bug with incorrect date-time datatypes handling
0.1.232022-09-2617116added connection string identifier
0.1.222022-09-2116766Update JDBC Driver version to 3.13.22
0.1.212022-09-1415668Wrap logs in AirbyteLogMessage
0.1.202022-09-0116258Emit state messages more frequently
0.1.192022-08-1915797Allow using role during oauth
0.1.182022-08-1814356DB Sources: only show a table can sync incrementally if at least one column can be used as a cursor field
0.1.172022-08-0915314Discover integer columns as integers rather than floats
0.1.162022-08-0415314(broken, do not use) Discover integer columns as integers rather than floats
0.1.152022-07-2214828Source Snowflake: Source/Destination doesn't respect DATE data type
0.1.142022-07-2214714Clarified error message when invalid cursor column selected
0.1.132022-07-1414574Removed additionalProperties:false from JDBC source connectors
0.1.122022-04-2912480Query tables with adaptive fetch size to optimize JDBC memory consumption
0.1.112022-04-2710953Implement OAuth flow
0.1.92022-02-2110242Fixed cursor for old connectors that use non-microsecond format. Now connectors work with both formats
0.1.82022-02-1810242Updated timestamp transformation with microseconds
0.1.72022-02-1410256Add -XX:+ExitOnOutOfMemoryError JVM option
0.1.62022-01-259623Add jdbc_url_params support for optional JDBC parameters
0.1.52022-01-199567Added parameter for keeping JDBC session alive
0.1.42021-12-309203Update connector fields title/description
0.1.32021-01-119304Upgrade version of JDBC driver
0.1.22021-10-217257Fixed parsing of extreme values for FLOAT and NUMBER data types
0.1.12021-08-134699Added json config validator