Looking for the previous version? View v2024.06 documentation →
Snowflake Connection Profile — Non-JDBC
Create a Snowflake connection profile in Data Trust using the native Non-JDBC connector with individual parameter fields for host, account, database, schema, role, and warehouse.
Overview
Data Trust supports Snowflake Non-JDBC connections using Snowflake’s native connector parameters. This connection type uses individual fields (scheme, host, port, user, account, db, schema, role, warehouse) rather than a single JDBC URL, making it easier to configure and less prone to URL-formatting errors.
Prerequisites
- You are logged in to Data Trust with an Admin Pro-User role.
- You have your Snowflake account identifier (e.g., account.snowflakecomputing.com), database name, schema, role, warehouse, and user credentials.
Creating a Snowflake Non-JDBC Connection
Path: Data Trust › Admin Console › Connection Explorer › + New ConnectionFigure 1: Navigate to Admin Console › Connection Explorer.
Open Admin Console from the left navigation and select Connection Explorer to manage all connection profiles.
Figure 2: Connection Explorer — click “+ New Connection” to create a Snowflake Non-JDBC profile.
Click + New Connection in the top-right corner of the Connection Explorer to open the Create Connection form.
- Click + New Connection.
Figure 3: Create Connection page — enter a Connection Name and select “Snowflake” from the Source Name dropdown.
Enter a unique Connection Name (e.g., Snowflake Connection). Select Snowflake from the Source Name dropdown. Leave Type Of Connection as Non JDBC (the default for Snowflake). The right panel immediately populates with Snowflake-specific parameter fields.
- Enter a unique Connection Name.
- Select Snowflake from the Source Name dropdown.
- Keep Type Of Connection as Non JDBC.
Figure 4: Snowflake Non-JDBC connection parameters — scheme, host, port, user, Password, account, db, schema, role, and warehouse.
The Snowflake Non-JDBC form provides individual fields for each connection parameter. This is cleaner than a JDBC URL because each value is validated separately. Fill in each field as described in the table below.
| Field | Description | Example |
|---|---|---|
| scheme | Connection scheme (leave as default if unsure) | https |
| host | Snowflake account hostname | account.us-east-1.snowflakecomputing.com |
| port | Snowflake port (default 443) | 443 |
| user | Snowflake username | svc_datatrust |
| Password | Snowflake password for the user | — |
| account | Snowflake account identifier (without .snowflakecomputing.com) | myaccount.us-east-1 |
| db | Default database to connect to | SALES_DB |
| schema | Default schema within the database | PUBLIC |
| role | Snowflake role to assume | ANALYST |
| warehouse | Snowflake virtual warehouse to use | COMPUTE_WH |
Figure 5: The “user” field info tooltip explains the expected Snowflake username format.
Clicking the (i) icon next to the user field displays a tooltip with guidance on the expected Snowflake username format. Each field with an (i) icon has contextual help — hover over or click the icon if you are unsure of the expected value.
Figure 6: The Password field with its visibility toggle (eye icon) and info (i) icon for guidance.
The Password field shows a masked input. Use the eye icon to reveal it for verification. The (i) icon provides a tooltip about Snowflake password requirements. The adjacent question-mark (?) icon links to additional documentation.
Figure 7: Connection Parameters with scheme and host values beginning to be entered.
As you fill in the form, each field shows a placeholder hint (e.g., dq44313.us-east-1.snowflakecomputing.com for the host field) that illustrates the expected format.
Figure 8: All Snowflake Non-JDBC connection parameters fully populated — ready for Additional Settings configuration.
All ten connection parameter fields are now filled in. The values are redacted here for security. Verify each value carefully, especially account (must match the Snowflake account identifier exactly) and warehouse (the warehouse must be running to allow test connections).
- Click the Additional Settings tab and configure parallelism, user group access, and any query timeout as needed.
Figure 9: Additional Settings tab — configure Default Parallelism, Max Parallelism, packet sizes, User Groups, and optional Query Timeout.
The Additional Settings tab controls query execution performance and access. Snowflake query performance is also governed by the warehouse size — set parallelism values that align with your Snowflake warehouse concurrency limits. Assign the relevant User Groups to control which teams can use this Snowflake connection.
Figure 10: The user info (i) button provides help for the user field on the Edit Connection page.
On the Edit Connection page, the (i) icons remain available next to each field for contextual help. This is especially useful when editing an existing Snowflake connection to verify which account format was used.
- Click Test Connection to verify the Snowflake credentials and warehouse connectivity.
A green “Test Connection Successful!” toast confirms the connection is valid.
Figure 11: Green “Test Connection Successful!” toast — the Snowflake Non-JDBC connection is verified and ready to save.
The green toast confirms Data Trust authenticated against Snowflake using the supplied credentials and warehouse. If the test fails, check the account identifier format, confirm the warehouse is running and not suspended, and verify the user has USAGE privilege on the specified database and schema.
- Click Save to create the profile.
Figure 12: Click Save to persist the Snowflake connection profile.
Clicking Save stores all ten connection parameters and the Additional Settings permanently. The profile is immediately available for use in Query Studio, Scenario Builder, and all other Data Trust modules.
The Snowflake Non-JDBC profile appears in the Connection Explorer listing.
Figure 13: Connection Explorer — the Snowflake connection profile is now listed and available for use across Data Trust.
The new Snowflake profile appears in the Connection Explorer table with Source Name Snowflake. Its Last Status updates after the first successful test or execution. The profile is now available in the Connection dropdown in Query Studio and Scenario Builder.