Snowflake sources use their own form with the steps General, Connection and Datetime. Use this page to sign in with a key pair or a password, choose the warehouse and scope, and set how datetime values are read.
The Sign-in card holds the account and the credentials:
orgname-accountname form or as the account host, such as xy12345..For Key pair, fill in:
., . and . files. If the file cannot be read, the form shows "Could not read the key file:" and the reason.For Password, fill in Password.
Switching Method clears the secrets of the method you leave. Enter them again if you switch back.
After you save, the form never shows the key or the password again: the field reads Stored private key or Stored password, with Replace. If your administrator turned on the re-entry setting, changing Account or Username clears the stored value and asks for it again; Connect a database covers stored passwords and keys in general.
The Compute & scope card sets where the source runs and what it reads.
| Setting | Required | What to enter |
|---|---|---|
| Warehouse | Yes | The warehouse the source runs with, for example COMPUTE_WH |
| Role | No | The role the source runs as. Leave it empty to use the user's default role. |
| Database | Yes | The database to read from, for example ANALYTICS |
| Schema | No | Leave it empty to use all schemas. |
Enter names as Snowflake shows them. Snowflake stores unquoted names in upper case, so type COMPUTE_WH rather than compute_wh.
On the Datetime step, Timezone and Datetime values decide how the source's timestamps are read on load. If the connection test detected the source timezone, the step suggests it and you can apply it. The settings and the rules that always apply to values are described on Timezones and datetime values.
Before you save, the step shows a summary: Name, Account, Username, Method (Key pair or Password), Warehouse, Role, Database and Schema. An empty Role or Schema reads as Default role of the user or All schemas. Click Add to create the source. Once it is saved, import its tables.
Key pair (recommended) is the default. It signs in with an RSA private key whose public key is registered on the Snowflake user. Choose Password to sign in with a password instead; switching Method clears the secrets of the method you leave.
The account identifier, in the orgname-accountname form or as the account host, such as xy12345..
., . and . files. If the file cannot be read, the form shows "Could not read the key file:" and the reason.
Switching Method clears the secrets of the method you leave, so the key and the passphrase are removed when you pick Password. Switch back to Key pair (recommended) and enter them again.
No. Leave Private key passphrase empty for an unencrypted key. Enter a passphrase only when the key file is encrypted.
Account, Username, Warehouse and Database are required. In key-pair mode the Private key (PEM) is required; in password mode it is the Password. Role, Schema and the passphrase are optional. The form names any required field you leave empty, for example "Account is required" or "Private key is required".
Enter names as Snowflake shows them. Snowflake stores unquoted names in upper case, so type COMPUTE_WH rather than compute_wh.
An empty Role means the source runs as the user's default role. An empty Schema means all schemas are used. The summary on the last step shows Default role of the user and All schemas for them.
The form opens on the Connection step, and the submit button reads Save. Name and Code are locked in edit mode.
The rows Name, Account, Username, Method (Key pair or Password), Warehouse, Role, Database and Schema. Click Add to create the source.