Snowflake: 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.
Database Connection
Snowflake
Name
Enter a name for the new connection.
Connection Parameters
|
Parameter |
Description |
|---|---|
|
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 Parameters
Select an authentication method:
Basic
Uses Snowflake username and password.
|
Parameters |
Description |
|---|---|
|
Username and Password |
The username and password to connect to the specified account, warehouse, database, and schema. |
Browser-based SSO
Uses Single Sign-On to connect via an external web browser.
|
Parameters |
Description |
|---|---|
|
Username |
After entering your username, you will be redirected to the web browser to complete the login. This method supports MFA (Multi-Factor Authentication). Note Browser-based SSO is not supported on FME Flow.
|
Key Pair
Uses an RSA key pair, username, and password to connect. A public key must be assigned to the user, and a file path to the file containing the private key must be accessible by FME.
This method supports MFA (Multi-Factor Authentication).
|
Parameters |
Description |
|---|---|
|
Key File |
Enabled with Key Pair authentication. The path to the private key file required to connect via Key Pair authentication. |
|
Username and Password |
|
Multi-factor Authentication
MFA can be used to connect to Snowflake via the Snowflake JDBC driver. Snowflake’s MFA authentication requires the Duo Mobile Application.
|
Parameters |
Description |
|---|---|
|
Username and Password |
By default, the Duo Push authentication mechanism is used when a user is enrolled in MFA. When you connect, Duo will send a push notification. |
OAuth Connection
Connects using one of the following web services:
-
Microsoft Azure Active Directory (Client Credentials) – This OAuth 2.0 web service is suitable for FME Flow automated, server-to-server workflows where user interaction is not required. This web service does not prompt for Microsoft Entra authentication.
-
Microsoft Azure Active Directory (Template) – This web service is suitable for FME Form. It is ideal for interactive workflows where the user manually runs the workspace and can authenticate when prompted.
- Snowflake OAuth uses Snowflake’s built-in OAuth service to provide OAuth-based authentication.
|
Parameters |
Description |
|---|---|
|
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.
For more information, see Snowflake OAuth overview on the Snowflake documentation website. |
Snowpark Container Service
Available when FME is running in a Snowpark Container Service container.
|
Description |
|---|
|
All communication between FME and Snowflake occurs inside Snowflake’s environment, ensuring that only trusted users and workloads can access its container services. Note The only recommended scenario for running FME inside Snowpark Container Services is for use with remote engines.
|
When enabled, this parameter will allow the JDBC connection string and properties to be specified directly, in order to connect to the database.
|
Input |
Description |
|---|---|
|
Connection String |
The connection string for the database to which you are connecting. |
|
Password |
An optional parameter if the connection requires a password. |
|
Mask Connection Details |
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>=************,
Connection strings for connections whose parameters are embedded in the workspace are not masked, regardless of this setting.
|
|
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. |