Advanced Analytica Advanced Analytica: IBOM
← All connectors
Snowflake logo

Source connector

Snowflake

Set up Snowflake as a source and move its data into your chosen destination.

Version 2.0.8 certified generally available

import KeypairExample from ‘@site/static/_snowflake_keypair_generation.md’;

Snowflake

:::danger Username and password authentication deprecated From version 2.0.0, username and password authentication is deprecated. It will be removed in a future release. Use Key pair authentication or a programmatic access token to connect to Snowflake.

This change aligns with Snowflake’s deprecation of single-factor password sign-ins. Snowflake is introducing strong authentication for all users between August and October 2026, one account at a time. Once enabled for your account, password-only Airbyte logins will fail.

If you currently use username and password authentication, follow the Snowflake Migration Guide. It explains how to migrate to key pair authentication or a programmatic access token. :::

Overview

The Snowflake source syncs your data from Snowflake. It supports Full Refresh and Incremental syncs. You can copy only new or updated data. Alternatively, copy every configured row and column whenever a sync runs.

The Snowflake source connector uses the source-jdbc code base. It uses JDBC 3.23.1 Snowflake driver, as described in the Snowflake documentation.

Resulting schema

The Snowflake source doesn’t change your warehouse schema. However, the connected destination might change the resulting schema. See the destination’s documentation for details.

Features

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

Incremental sync

Incremental sync lets you replicate only data added or updated since the previous sync. A cursor field tracks the sync state.

How incremental sync works

During an incremental sync, the connector:

  1. Identifies new records: Uses a WHERE cursor_field > last_cursor_value clause to fetch only records newer than the last synced value
  2. Maintains order: Applies ORDER BY cursor_field ASC to process records in the correct sequence
  3. Tracks state: Stores each sync’s maximum cursor value as the next sync’s starting point

Supported cursor data types

You can use the following JDBC data types as cursor fields:

Date and Time Types:

  • TIMESTAMP_WITH_TIMEZONE
  • TIMESTAMP
  • TIME_WITH_TIMEZONE
  • TIME
  • DATE

Numeric Types:

  • TINYINT
  • SMALLINT
  • INTEGER
  • BIGINT
  • FLOAT
  • DOUBLE
  • REAL
  • NUMERIC
  • DECIMAL

String Types:

  • NVARCHAR
  • VARCHAR
  • LONGVARCHAR

Choose a cursor field

For effective incremental syncs, choose cursor fields that:

  • Are monotonically increasing: Use values that always increase, such as auto-incrementing IDs or creation timestamps
  • Are never updated: Avoid fields that might change after record creation
  • Have unique values: Duplicate values are supported, but can cause records to be skipped or synced again
  • Are indexed: Improve query performance on large tables

Good cursor field examples:

  • CREATED_AT or UPDATED_AT timestamp columns
  • Auto-incrementing ID columns
  • Sequence-generated numeric fields

Avoid using:

  • Fields that can be updated after creation
  • Fields with many duplicate values
  • Fields that can contain NULL values

Snowflake considerations

Timezone Handling: The connector handles Snowflake’s TIMESTAMPLTZ data type, which is a timestamp with a local timezone. It automatically converts the value to TIMESTAMP_WITH_TIMEZONE for consistent processing.

Data Type Precision: Snowflake’s numeric types retain their precision during sync. Make sure your destination supports your cursor fields’ precision.

Configure incremental sync

To configure incremental sync in Airbyte:

  1. Create or edit your connection in the Airbyte UI
  2. Select your source tables that you want to sync incrementally
  3. Choose “Incremental | Append” sync mode for each table
  4. Select a cursor field from the list of available fields
  5. Verify the cursor field meets the criteria above, including increasing consistently and never being updated

The Airbyte UI checks whether your chosen cursor field supports incremental sync. It also shows the supported data types for your table schema.

Troubleshoot incremental sync

Cursor field validation errors: If you receive an invalid cursor field error, check that the field exists in your table. It must also use a supported data type listed above.

Duplicate cursor values: The connector processes every record sharing the same cursor value. As a result, some records might be synced more than once across separate sync runs.

NULL cursor values: Incremental sync excludes records with NULL cursor field values. Make sure your cursor field has a NOT NULL constraint or default value.

State reset: To sync all data again, reset the connection’s state in the Airbyte UI. The next sync will then work like a full refresh.

Get started

Requirements

You’ll need this information to configure the Snowflake source:

  1. Host
  2. Role
  3. Warehouse
  4. Database
  5. Schema
  6. Username (not required for programmatic access token authentication)
  7. Private key or programmatic access token (password authentication is deprecated but still supported)
  8. JDBC URL Params (Optional)

Also create a dedicated, read-only Airbyte service user and role. Give them access to every schema you need to replicate.

Setup guide

Connection parameters

For more information about Snowflake connection parameters, see the Snowflake documentation.

This optional step is strongly recommended for better permission control and auditing. Alternatively, you can use Airbyte with an existing database user.

First, generate a key pair as described in Key pair authentication. Then run the following commands against your database to create a dedicated user. Replace <public_key_value> with your rsa_key.pub file’s contents, excluding the -----BEGIN PUBLIC KEY----- and -----END PUBLIC KEY----- header and footer lines.

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

BEGIN;

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

-- create Airbyte service user with key pair authentication
CREATE USER IF NOT EXISTS $AIRBYTE_USERNAME
TYPE = SERVICE
DEFAULT_ROLE = $AIRBYTE_ROLE
DEFAULT_WAREHOUSE= $AIRBYTE_WAREHOUSE;

-- assign the RSA public key to the service user
ALTER USER IDENTIFIER($AIRBYTE_USERNAME) SET RSA_PUBLIC_KEY='<public_key_value>';

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

COMMIT;

You can limit this grant to specific schemas instead of the whole database. To replicate multiple Snowflake databases, rerun the command above and grant access to every relevant schema. You’ll need separate sources for the same database’s different schemas.

Your database user is now ready to use with Airbyte.

Authentication

The Snowflake source supports these authentication methods:

  • Key pair authentication (recommended)
  • Programmatic access token
  • Username and password (deprecated, see the migration guide)

Connection fields

These fields apply to every authentication method:

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. A pasted https:// prefix, trailing / or :443 is accepted and removed; on Airbyte Cloud a console URL with a path (for example https://app.snowflake.com/<org>/<account>) or credentials fails the connection test with Enter only the host domain in Host (for example account.snowflakecomputing.com), without a path or credentials.
RoleThe role you created for Airbyte to access Snowflake. Example: AIRBYTE_ROLE
WarehouseThe warehouse you created for Airbyte to sync data into. Example: AIRBYTE_WAREHOUSE
DatabaseThe database you created 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 to allow Airbyte to access the database. Example: AIRBYTE_USER. Not required for programmatic access token authentication.
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

Key pair authentication

In the Airbyte UI, select Key Pair Authentication as the authorization method and enter the username. Paste your complete rsa_key.p8 private key file, including the -----BEGIN ... PRIVATE KEY----- header and footer. If the key is encrypted, enter the passphrase.

Programmatic access token authentication

To authenticate with a Snowflake programmatic access token, select Programmatic Access Token as the authorization method. Then provide the token. You don’t need a username because the token identifies its Snowflake user.

Create a programmatic access token in Snowflake with:

ALTER USER <user_name> ADD PROGRAMMATIC ACCESS TOKEN <token_name>
  ROLE_RESTRICTION = '<airbyte_role>'
  DAYS_TO_EXPIRY = <days>;

The token secret appears only when you create the token. Store it securely before closing the result.

By default, Snowflake requires ROLE_RESTRICTION for service users. It also requires a network policy before service users can generate or use programmatic access tokens. Your authentication policy can change this behaviour. If it restricts permitted methods, include PROGRAMMATIC_ACCESS_TOKEN in AUTHENTICATION_METHODS.

:::note Network policy required for Programmatic Access Token authentication For Programmatic Access Token authentication, the Snowflake user’s network policy must permit connections from Airbyte’s IP addresses. Add the Airbyte Cloud IP addresses to the PAT user’s network policy or the account-level network policy. :::

Username and password (deprecated)

Username and password authentication is deprecated from version 2.0.0. It will be removed in a future release. Existing sources continue working until Snowflake enforces strong authentication on your account. Follow the migration guide to switch to key pair authentication or a programmatic access token.

Network policies

By default, Snowflake permits users to connect from any computer or device IP address. A security administrator, such as a user with the SECURITYADMIN role, can create a network policy. Users with higher roles can also create one. The policy can permit or deny one IP address or a list of addresses.

If you can’t connect with Airbyte Cloud, make sure its IP addresses are on your allowed list.

Run the SHOW PARAMETERS command to check for an account-level or user-specific network policy.

Account

SHOW PARAMETERS LIKE 'network_policy' IN ACCOUNT;

User

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

For more information, see the official Snowflake documentation.

Troubleshooting

  • check or discovery is very slow, or lists tables from other schemas (before 2.0.4). The Snowflake JDBC driver treated _ and % in the Schema option as LIKE wildcards. It then scanned the whole database because SCHEMA_A also matched SCHEMAXA. From version 2.0.4, the option uses an exact name. On older versions, add ENABLE_WILDCARDS_IN_SHOW_METADATA_COMMANDS=false to JDBC URL Params. If you used % or _ to select several schemas, add ENABLE_WILDCARDS_IN_SHOW_METADATA_COMMANDS=true to JDBC URL Params to retain that behaviour.
  • Key pair authentication fails with JWT token is invalid. Snowflake rejected the login, and retrying won’t resolve the problem. The private key might not match the RSA public key registered for the user. Alternatively, the Username or Server URL might be wrong. The clock on the machine running Airbyte might also be incorrect. Compare the fingerprint from DESCRIBE USER <user> (RSA_PUBLIC_KEY_FP) with your key. Alternatively, register the public key again with ALTER USER <user> SET RSA_PUBLIC_KEY='...'. To find the exact cause, note the ID in brackets after the error (JWT token is invalid. [<id>]). Ask a Snowflake administrator to run SELECT SYSTEM$GET_LOGIN_FAILURE_DETAILS('<id>');. See Snowflake’s key pair troubleshooting guide. Older versions reported this error as an expired session token that would reconnect automatically. It isn’t an expired token. The connection will fail until you correct the key pair configuration.
  • Incremental sync on a TIMESTAMP_NTZ cursor misses rows (before 2.0.4). Snowflake sessions default to the America/Los_Angeles time zone, which changed the cursor bound. This was fixed in version 2.0.4. On older versions, add TIMEZONE=UTC to JDBC URL Params as a workaround.

IP allow list

If Airbyte Cloud access is restricted to specific IPs, add the Airbyte Cloud IP addresses to your allow list.

Changelog

Expand to review
VersionDatePull RequestSubject
2.0.82026-10-3090171Test-only: share one seeded schema across live tests, trim the cursor timezone matrix and run live tests concurrently. No connector runtime change.
2.0.72026-10-2989647Upgrade to Bulk CDK 1.2.3: fix critical CVEs in Apache MINA (mina-core 2.0.31), MINA SSHD 2.20.0 and BouncyCastle 1.86.
2.0.62026-10-2990173Discover now skips a view that references a column dropped from its base table instead of failing; syncs of such a view fail with a configuration error that explains how to fix it.
2.0.52026-10-1488501Upgrade to Bulk CDK 1.1.16; a pasted https:// prefix, trailing / or :443 in Host is now accepted, and on Airbyte Cloud a URL with a path or credentials is rejected with an explicit message before the connection is attempted.
2.0.42026-10-1487471TIME columns are no longer emitted as NULL; TIMESTAMP_NTZ cursor bounds are bound as NTZ, so a non-UTC session TIMEZONE no longer shifts the incremental window (h/t @ZenonRad, 83800); 9999-12-31 23:59:59.999999999 no longer rounds into year 10000; check fails fast on a wrong warehouse, database or schema; the Schema option is an exact name instead of a LIKE pattern (_ or % made check list the whole database, took minutes on large accounts and leaked other schemas’ tables, columns and primary keys; 87000, 86998); ~2 s less connection latency per query (driver platform detection off); private key written to a temp file; the JWT token is invalid error now also points to the Server URL, the host clock and SYSTEM$GET_LOGIN_FAILURE_DETAILS for the exact cause; snowflake-jdbc 4.3.4.
2.0.32026-10-1387510Report invalid key pair (JWT) authentication as a configuration error with actionable guidance instead of a misleading temporary session-expiry error.
2.0.22026-10-0988432Upgrade to Bulk CDK 1.1.14.
2.0.12026-09-2385081 & 86936Discover no longer fails entirely when a single view or object is invalid or inaccessible; the offending stream is skipped (h/t @jrbarkin).
2.0.02026-09-0385331Deprecate username/password authentication; key pair authentication or a programmatic access token is now recommended. Username/password will be removed in a future release.
1.1.22026-08-2184927Bump Bulk CDK extract version from 1.0.1 to 1.1.10
1.1.12026-07-2182705Fix incremental sync silently dropping rows at the cursor’s upper bound by rounding timestamp precision up instead of down
1.1.02026-05-2878481Support Snowflake Programmatic Access Token authentication.
1.0.112026-05-0577787Make the hidden additional properties fields in spec optional. No functional change.
1.0.102026-03-1374834Truncate timestamp precision to 6 digits (microseconds) to prevent precision errors in destinations
1.0.92025-09-1674081Security update
1.0.82025-09-1666311Change CDK version to 0.1.31
1.0.72025-09-1666200Fix sampling bug for DefaultJdbcCursorIncrementalPartition
1.0.62025-09-1266226Fix schema filtering functionality in versions 1.0.0+ - resolves “discovered zero tables” error and enables proper schema-level filtering
1.0.52025-07-2863780Fix ts data type for snowflake
1.0.32025-07-2263713Revert base image from 2.0.3 to 2.0.2 to fix SSL certificate errors
1.0.22025-07-1462939Update base image to 2.0.3
1.0.12025-07-1162929Update test dependencies
1.0.02025-06-2461535Replace community support connector with Airbyte certified connector
0.3.62025-01-1051504Use a non root base image
0.3.52024-12-1849911Use a base image: airbyte/java-connector-base:1.0.0
0.3.42024-10-3148073Upgrade jdbc driver
0.3.32024-06-2840424Support Snowflake key pair authentication
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-1420346Consolidate 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
Advanced Analytica

Most businesses are sitting on information they can’t use at speed. The people who hold it are busy, and when they leave, the knowledge goes with them. The documents are static, and the processes around them weren’t designed for AI.

Advanced Analytica works with these businesses to turn that information into structured data assets. Once they're integrated, AI systems can govern it, and the business can use it. We bring in the strategy, the specification and the AI skills to rework how the business operates.

MOVE FAST. STAY SAFE.