Snowflake Connector

This node creates a connection to a Snowflake database using the selected Snowflake JDBC driver. For further information about Snowflake see the Snowflake documentation.

This node uses the selected driver's JDBC URL template to create the concrete database URL. Field validation in the dialog depends on whether the (included) tokens referencing them are mandatory or optional in the template.

Options

Connection settings

This tab contains the main setting to connect to a Snowflake database. For more details about the different connection parameters see the Snowflake documentation.

Database Dialect
Choose the registered database dialect here.
Database Driver

Choose the JDBC driver to connect to the database here. If you select "Use latest driver version available" upon execution the node will automatically use the driver with the latest (highest) driver version that is available for the current database type. This has the advantage that you do not need to touch the workflow after a driver update. However, the workflow might break in the rare case that the behavior of the driver e.g. type mapping changes with the newer version.

If this option is not enabled, you can select a specific version of the registered drivers via the drop-down list. Additional drivers can be registered via KNIME's preference page "KNIME -> Databases". For more details on how to register a new driver see the database documentation.

Full account name
Specifies the full name of your account (provided by Snowflake). Note that your full account name might include additional segments that identify the region and cloud platform where your account is hosted e.g. xy12345.us-east-2.aws, xy12345.us-central1.gcp or xy12345.west-us-2.azure.
The domain .snowflakecomputing.com will be appended automatically to the full account name.
Virtual warehouse
Specifies the virtual warehouse to use once connected, or an empty string. The specified warehouse should be an existing warehouse for which the specified default role has privileges.
After connecting, the USE WAREHOUSE command can be executed with the DB SQL Executor node to set a different database for the session.
Default access control role (optional)
Specifies the default access control role to use in the Snowflake session initiated by the driver. The specified role should be an existing role that has already been assigned to the specified user for the driver. If the specified role has not already been assigned to the user, the role is not used when the session is initiated by the driver.
For more information about roles and access control, see Access Control in Snowflake.
Default database (optional)
Specifies the default database to use once connected, or an empty string. The specified database should be an existing database for which the specified default role has privileges.
After connecting, the USE DATABASE command can be executed with the DB SQL Executor node to set a different database for the session.
Default schema (optional)
Specifies the default schema to use for the specified database once connected, or an empty string. The specified schema should be an existing schema for which the specified default role has privileges.
After connecting, the USE SCHEMA command can be executed with the DB SQL Executor node to set a different schema for the session.
None
Sending no credentials is required for some Snowflake specific logins such as SSO. Please refer to the Snowflake documentation for any further setup steps that might be required.
Username
Sending only the user name is required for some Snowflake specific logins such as key pair authentication. Please refer to the Snowflake documentation for any further setup steps that might be required.
Credentials
If checked, the credentials (user and password) are used as defined on the workflow. The credential name links to the specified user and password.
Username & password
Your log-in user name and password for the database. Note that the password is encrypted before storage and decrypted afterwards for being used internally.

JDBC Parameters

This tab allows you to define JDBC driver connection parameter. The value of a parameter can be a constant, variable, credential user, credential password or KNIME URL.
The TIMEZONE parameter is added with the default time zone of the KNIME runtime environment to prevent mapping problems when working with date and time data types. For more details about the parameter see the Snowlfake documentation or ask your Snowflake administrator.
The application parameter is added as default to all Snowflake connections to track the usage of KNIME Analytics Platform as Snowflake client (for details go here). If you are not comfortable sharing this information with Snowflake you can remove the parameter. However, if you want to promote KNIME as a client with Snowflake leave the parameter as is.

JDBC Parameters
For more information about the supported driver properties see the Snowflake documentation.

Advanced

This tab allows you to define KNIME framework properties such as connection handling, advanced SQL dialect settings or logging options.

Advanced Parameters
For more information about the supported parameters see the KNIME Database Extension Guide.

Input Type Mapping

This tab allows you to define rules to map from database types to KNIME types.

Mapping by Name
Columns that match the given name (or regular expression) and database type will be mapped to the specified KNIME type.
Mapping by Type
Columns that match the given database type will be mapped to the specified KNIME type.

Output Type Mapping

This tab allows you to define rules to map from KNIME types to database types.

Mapping by Name
Columns that match the given name (or regular expression) and KNIME type will be mapped to the specified database type.
Mapping by Type
Columns that match the given KNIME type will be mapped to the specified database type.

Input Ports

Icon

To use this input port, you must attach the Microsoft Authenticator. Choose one of the OAuth2 authentication types and enter the custom scope you want to use. The scope is specific to the setup of your Azure Entra ID (formerly Azure Active Directory). For further details on how to create a scope or where to find it see the Snowflake documentation.

When available the node will set the authenticator as well as token JDBC parameter automatically based on the information from the connected Microsoft Authenticator node. Depending on your database setup you might need to specify additional JDBC parameters which are described in the Snowflake documentation.

Output Ports

Icon
Snowflake DB Connection.

Views

This node has no views

Workflows

Links

Developers

You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.