Snowflake connection

Introduction

A Snowflake connection, created using the Snowflake connector, establishes access to Snowflake. Once a connection is configured, you can create instances of Snowflake activities associated with that connection to be used either as sources (to provide data in an operation) or as targets (to consume data in an operation).

Create or edit a Snowflake connection

A new Snowflake connection is created using the Snowflake connector from one of these locations:

• The design component palette's Project endpoints and connectors tab (see Design component palette).
• The Global Endpoints page (see Create a global endpoint in Global Endpoints).

An existing Snowflake connection can be edited from these locations:

• The design component palette's Project endpoints and connectors tab (see Design component palette).
• The project pane's Components tab (see Component actions menu in Project pane Components tab).
• The Global Endpoints page (see Edit a global endpoint in Global Endpoints).

Configure a Snowflake connection

Each user interface element of the Snowflake connection configuration screen is described below.

• Connection name: Enter a name to use to identify the connection. The name must be unique for each Snowflake connection and must not contain forward slashes / or colons :. This name is also used to identify the Snowflake endpoint, which refers to both a specific connection and its activities.

• Authentication: Select the authentication type, one of Key-Pair, OAuth, or Password (Deprecated):

  • Key-Pair: Select this option to use a key-pair for authentication:

    • Host name: Enter the Snowflake host name. This is the Snowflake account name (such as example-account123) and the Snowflake domain name of snowflakecomputing.com concatenated together, such as example-account123.snowflakecomputing.com.

    • User name: Enter the Snowflake username.

    • Private key specification: Select either Unencrypted or Encrypted key to identify the type of private key used.

    • Private key: Enter the private key. For more information, refer to the Snowflake Key-pair authentication and key-pair rotation documentation.

    • Passphrase: If Encrypted key is selected for Private key specification, enter the passphrase associated with the encrypted private key.

  • OAuth: Select this option to use 3-legged OAuth 2.0 for authentication:

    • Host name: Enter the Snowflake host name. This is the Snowflake account name (such as example-account123) and the Snowflake domain name of snowflakecomputing.com concatenated together, such as example-account123.snowflakecomputing.com.

    • User name: Enter the Snowflake username.

    • OAuth application: Select a Snowflake connector application configured in the Management Console App Registrations page. For more information on configuring a Snowflake connector application in the App Registrations page, refer to the Snowflake 3-legged OAuth prerequisites.

    • Log in with Snowflake: Click to authenticate through Snowflake in a separate browser tab and provide consent for Jitterbit to access the Snowflake application.

  • Password (Deprecated): Select this option to use a password for authentication:

    • Host name: Enter the Snowflake host name. This is the Snowflake account name (such as example-account123) and the Snowflake domain name of snowflakecomputing.com concatenated together, such as example-account123.snowflakecomputing.com.

    • User name and Password: Enter the Snowflake username and password.

      Snowflake user TYPE property must be set to LEGACY_SERVICE and future deprecation of single-factor authentication

      Snowflake has announced the upcoming deprecation of single-factor authentication, which affects integrations that connect to Snowflake using a password. All users of the Snowflake connector using the Password (Deprecated) authentication type are affected.

      Recommended user action

      User action is required in two phases:

      1. By March 31, 2025, the TYPE property of the user account you use to connect to Snowflake must be set to LEGACY_SERVICE in order to continue using password-based authentication (see Types of users). Without user action, existing integrations using Snowflake single-factor password authentication are expected to begin failing in April 2025.

      2. By November 2025, you must update the type of authentication used to connect to Snowflake to OAuth 2.0 or key-pair authentication. At this time, password-based authentication will no longer be supported.

• Account: Enter the Snowflake account name.

• Database name: Enter the Snowflake database name.

• Schema name: Enter the Snowflake schema name.

• Optional settings: Click to expand additional optional settings:

  • Role: Enter the Snowflake role. The available roles are GENERAL, PUBLIC, and READONLY.

  • Warehouse Name: Enter the Snowflake warehouse name.

  • Escape special characters: When selected, a single quote character (') is escaped (\') when it is present in an Insert or Invoke Stored Procedure activity's request payload.

    When unselected (default), and a single quote character (') is present in a request payload, a syntax error is returned at runtime.

• Use quote for Snowflake identifiers: Select this option to use quotes around Snowflake identifiers such as table names to preserve their case instead of converting their case to uppercase, which can cause an error. By default this is selected.

• Test: Click to verify the connection using the provided configuration. When the connection is tested, the latest version of the connector is downloaded by the agent(s) in the agent group associated with the current environment. This connector supports suspending the download of the latest connector version by using the Disable Auto Connector Update organization policy.

• Save Changes: Click to save and close the connection configuration.

• Discard Changes: After making changes to a new or existing configuration, click to close the configuration without saving. A message asks you to confirm that you want to discard changes.

• Delete: After opening an existing connection configuration, click to permanently delete the connection from the project and close the configuration (see Component dependencies, deletion, and removal). A message asks you to confirm that you want to delete the connection.

Next steps

After a Snowflake connection has been created, you place an activity type on the design canvas to create activity instances to be used either as sources (to provide data in an operation) or as targets (to consume data in an operation).

Menu actions for a connection and its activity types are accessible from the project pane and design component palette. For details, see Actions menus in Connector basics.

These activity types are available:

• Get: Retrieves a CSV file of table or view data from Snowflake and is intended to be used as a source in an operation.

• Query: Retrieves a CSV file of table or view data from Snowflake and is intended to be used as a source in an operation.

• Merge: Inserts or updates a CSV file of table data into Snowflake and is intended to be used as a target in an operation.

• Invoke Stored Procedure: Invokes a stored procedure created in Snowflake and is intended to be used as a target in an operation.

• Update: Updates table data in Snowflake and is intended to be used as a target in an operation.

• Delete: Deletes table data and view data from Snowflake and is intended to be used as a target in an operation.

• Insert: Inserts table data (either as a CSV file or directly mapped to columns of a table) into Snowflake and is intended to be used as a target in an operation.