Connector
Snowflake
Read and write Snowflake over its SQL API. There is no driver to install, and picking a table shows its columns in the builder without running (or waking) a warehouse.
Settings
What the connection form asks for. Every connection has a Staging side, which it needs, and an optional Production side with values of its own; both ask for the same settings.
| Account | Your account identifier, e.g. myorg-myaccount (or the older abc12345.us-east-1 form). |
| Endpoint (optional) | Set only for a PrivateLink or custom host. Blank uses {account}.snowflakecomputing.com. |
| User | The Snowflake user the key below is registered against (ALTER USER … SET RSA_PUBLIC_KEY). |
| Private key | Paste the whole PEM, including the BEGIN/END lines; its line breaks are restored for you. Snowflake's SQL API is key-pair only: it has no password authentication. Stored encrypted, and never shown again after you save it. |
| Key passphrase | Only if the private key is encrypted. Stored encrypted, and never shown again after you save it. |
| Warehouse | The warehouse queries run on. Browsing tables and reading their columns needs none, so this is only required once you actually run something. |
| Database | |
| Schema | |
| Role | Optional role to assume. Blank uses the user's default role. |
Testing the connection
Test signs in with the key pair and runs SHOW SCHEMAS. That proves the account, the user, the key and the role, and because SHOW needs no warehouse, testing never resumes one.
Good to know
- Snowflake's SQL API signs in with a key pair only; it has no password sign-in. Paste the whole private key, including its BEGIN and END lines; its line breaks are restored for you.
- Picking a table shows its columns without running a warehouse.