Connect to Snowflake

Connect to Snowflake with a .p8 key pair, an access token or browser sign-in. Warehouse, role, database and schema are optional.

Tablyne talks to Snowflake through the SQL API over HTTPS. The Snowflake SQL API does not accept a username and password, so the connection form offers three other ways to sign in.

Authentication

  • Key pair (.p8). This is the default. Pick a PKCS#8 private key file with the .p8 extension. Tablyne uses it to sign a JWT. An encrypted key is supported, and the form recommends one. The passphrase is stored in the system vault, not in the connection file or in exports.
  • Access token (PAT). Paste a Snowflake programmatic access token. It is kept in the system vault. The token’s user needs a network policy that allows your IP address.
  • Browser (SSO). Tablyne opens your browser for an OAuth sign-in and waits for you to finish. If the account has the local OAuth integration disabled, the sign-in fails and the error tells you to use the key or a token instead.

Account and context

Enter your account identifier and user. Warehouse, role, database and schema are optional. When you leave one empty, Snowflake uses the default of that user, and Tablyne does not send the field at all.

You also set a query timeout in seconds, and the size in GiB above which the console asks before running.

Testing the connection

The test button runs SHOW DATABASES and reports the time it took. It does not read any table.

Each console tab keeps its own warehouse, role, database, schema and timeout. Changing them in one tab does not change the connection or the other tabs.