.avif)
How Ridge works with Snowflake
What you can do
- Connect to Snowflake over ODBC with key-pair (JWT) authentication
- Reference a table directly, or shape it with a custom SQL query
- Refresh on a schedule with standard cron expressions
What you'll need
A few connection details link Ridge to your account. Collect these before you start.
Set up the connection
1 Create a Connection
On the Data page, click New Connection and choose Snowflake as the type. Enter the credentials you gathered, then save.
- Account identifier and Username
- Private key (PEM) and its password
2 Create a Dataset
Back on the Data page, click New, select source Connection, and pick the Snowflake connection you just created. A Data Set points at a specific table and can carry its own query and refresh schedule.
3 Select a table, or write a query
Choose how Ridge reads from Snowflake. A direct table reference is simplest; custom SQL lets you filter and aggregate at the source.
4 Schedule ingestion
Set an ingestion schedule with standard cron syntax, then save. Ridge runs your query against Snowflake and stores the results, ready for analysis.
Best practices
A few habits keep ingestion secure and predictable.
Supported features & limitations
- Connects via the SnowflakeDSIIDriver ODBC driver with
Authenticator=SNOWFLAKE_JWT(key-pair auth) - Reads a table or query result via
odbc_query(...) - Validates the connection before ingestion with an
odbc_query(... 'SELECT 1')probe - Uses the DuckDB
nanodbcextension
- Key-pair (JWT) auth only — username/password authentication is not supported.
Troubleshooting
Most connection issues fall into four buckets. Expand the one that matches your error.
Invalid credentials
"marshaling private key failed", "could not parse PEM", "incorrect username or password", "JWT token is invalid", 401
Your PEM key or password is bad, or the JWT was rejected. Re-paste the PEM key (keep the newlines) and password, and confirm key-pair auth is registered on the user.
Insufficient permissions
"insufficient privileges", "access control", 403
The role lacks rights. Grant it read access to the object.
Resource not found
"does not exist or not authorized", "object does not exist", "account name", 404
The account identifier or object name is wrong. Fix the identifier.
Network unreachable
"could not resolve host", "timed out", "connection refused", ODBCHYT00/08S01
The host is unreachable or timed out. Check your egress allowlist and account host.
