Snowflake Non-Spatial: Add Database Connection

To define a new connection from the Connection parameter in a Snowflake format:

Select Add Database Connection. See database-specific parameters below, as well as the section Adding a Database Connection in a Workspace in Using Database Connections The new connection can be made visible only to the current user, or can be shared among multiple users.

Note To select an existing, previously defined connection, see the section Reusing a Database Connection in Using Database Connections

Database Connection

Snowflake

Name

Enter a name for the new connection.

Connection Parameters

Account Name

The full name of your Snowflake account.

For example, if you access your Snowflake System in a web browser using a URL like this:

https://mycompanyinc.snowflakecomputing.com/

then your full account name is mycompanyinc.

Note Your full account name might include additional segments that identify the region and cloud platform where your account is hosted. For detailed information and examples, see Connection Parameters in Snowflake Documentation.

Warehouse

The virtual warehouse to use once connected. The specified warehouse should be an existing warehouse. This parameter is case-sensitive.

Database

Specifies the default database to use once connected. The specified database should be an existing database. This parameter is case-sensitive.

Schema

Specifies the default schema to use once connected. The specified schema should be an existing schema. This parameter is case-sensitive.

Role

Specifies the default access control role to use in the session. The specified role should be an existing role that is already assigned to the specified user.

Note This parameter is case-sensitive.

Authentication

The method used for authentication.

Basic uses Snowflake username and password.
OAuth Connection connects using Microsoft Azure Active Directory OAuth 2.0 web service, or Client Credentials web service.
Browser-based SSO uses Single Sign-On (with a username and password) to connect via an external web browser. This method supports MFA (Multi-Factor Authentication).

Username and Password

The username and password to connect to the specified account, warehouse, database, and schema. These parameters are enabled when the Basic authentication method is selected.

OAuth Connection

The web connection to use to obtain a valid OAuth token. This option is enabled when the OAuth Connection authentication method is selected.

Note To connect using Microsoft Azure Active Directory OAuth 2, make sure that a valid Microsoft Azure Active Directory (AD) web service has been configured before creating a web connection.

A Microsoft Azure Active Directory (Template) web service has been provided in your FME installation. To configure a new Microsoft Azure AD web service, create a new web service from this template, replacing [TENANT_ID] and [OAUTH_SCOPE] with the appropriate values.

For more information, see Configure Microsoft Azure AD for External OAuth on the Snowflake documentation website.

For Client Credentials authentication, please create a new web connection using the provided Microsoft Azure Active Directory (Client Credentials) web service.

Advanced – Specify JDBC Connection

When enabled, this parameter will allow the JDBC connection string and properties to be specified directly, in order to connect to the database.

Option	Description
Connection String	The connection string for the database to which you are connecting.
Mask Connection Details	When this option is checked (set to Yes) – Connection strings and properties for database connections are masked in translation and error logs. Connection details may contain sensitive information, such as passwords. A masked connection string appears as: jdbc:<subprotocol>:********** While masked connection properties appear as: {<property_name1>=********, <property_name2>=********, ...} Warning** Connection strings for connections whose parameters are embedded in the workspace are not masked, regardless of this setting. When this option is left unchecked (set to No) – Connection strings and properties are logged in plain text.
Connection Property and Value	JDBC connections can be configured with driver-specific arbitrary name/value pairs. The name/value pairs can often be specified in either the Connection String or a Properties object (sometimes only in one way or the other). Name/value pairs entered here will be set in the order specified, then passed on in a Properties object. They do not require manual encoding of characters that are not safe in Connection Strings.

Option

Description

Connection String

The connection string for the database to which you are connecting.

Mask Connection Details

When this option is checked (set to Yes) – Connection strings and properties for database connections are masked in translation and error logs.

Connection details may contain sensitive information, such as passwords. A masked connection string appears as:

jdbc:<subprotocol>:************

While masked connection properties appear as:

{<property_name1>=************,
<property_name2>=************, ...}

Warning Connection strings for connections whose parameters are embedded in the workspace are not masked, regardless of this setting.

When this option is left unchecked (set to No) – Connection strings and properties are logged in plain text.

Connection Property and Value

JDBC connections can be configured with driver-specific arbitrary name/value pairs. The name/value pairs can often be specified in either the Connection String or a Properties object (sometimes only in one way or the other).

Name/value pairs entered here will be set in the order specified, then passed on in a Properties object. They do not require manual encoding of characters that are not safe in Connection Strings.