Connect Snowflake
Register Querio's public key, grant a Snowflake service user access, and verify a table query.
Connect Snowflake with a service user and Querio's managed key pair. Your Snowflake administrator registers the public key and grants access to the data you want to query.
Before you start
- You need permission to manage datasource credentials in Querio.
- Your Snowflake administrator needs permission to create the user and role, grant access, and assign a public key to the user.
- Choose a warehouse and one table with a result you can check. The SQL below uses example names; have the administrator replace them with yours.
If a Snowflake network policy restricts connections, use Copy IP Address in the Querio connection form and have the administrator check that the policy permits that source.
1. Create a service user
Have the administrator create a dedicated Snowflake service user. Keep its login name for Querio's User field:
CREATE USER QUERIO_SVC
LOGIN_NAME = 'QUERIO_SVC'
TYPE = SERVICE;An existing service user also works if its key, default role, and grants are suitable. Querio does not use a Snowflake password.
2. Create a least-privilege role
Have the administrator grant access to the warehouse and only the data this connection should read. Replace QUERIO_WH, ANALYTICS, PUBLIC, and ORDERS with your names:
CREATE ROLE QUERIO_READER;
GRANT USAGE ON WAREHOUSE QUERIO_WH TO ROLE QUERIO_READER;
GRANT USAGE ON DATABASE ANALYTICS TO ROLE QUERIO_READER;
GRANT USAGE ON SCHEMA ANALYTICS.PUBLIC TO ROLE QUERIO_READER;
GRANT SELECT ON TABLE ANALYTICS.PUBLIC.ORDERS TO ROLE QUERIO_READER;
GRANT ROLE QUERIO_READER TO USER QUERIO_SVC;
ALTER USER QUERIO_SVC SET DEFAULT_ROLE = 'QUERIO_READER';This gives the role warehouse, database, and schema USAGE, plus SELECT on one table. Snowflake documents this grant pattern. Grant SELECT on other tables or views as needed. Querio has no Snowflake Role field, so set the service user's default role to the role with these grants.
3. Add the RSA public key
- In Querio, open Settings > Datasources > Add datasource, choose Internal, then Snowflake.
- In Snowflake public key, select Copy key only and give the public key to the administrator through your approved channel.
- Have the administrator register it on the service user from step 1. Snowflake supports setting the user's
RSA_PUBLIC_KEYproperty:
ALTER USER QUERIO_SVC SET RSA_PUBLIC_KEY = 'COPIED_PUBLIC_KEY';Replace the placeholder with the copied key, without public-key delimiters. You can also select Copy ALTER USER to copy the statement with the key already filled in. Its user name is QUERIO_SVC; change that name if yours differs.
Querio uses a managed key pair. There is no private-key field for this connection. Copy the current public key from the form, not from an older guide.
4. Enter the connection details
In the same form, enter a Slug for the datasource and these Snowflake fields:
| Field | Example | Where to get it |
|---|---|---|
| Account | orgname-account_name | The client account identifier from Snowflake, without the Snowflake URL. |
| User | QUERIO_SVC | The service user's login name. |
| Warehouse | QUERIO_WH | A warehouse the user's default role can use. |
| Database | ANALYTICS | Optional default database. |
| Database schema | PUBLIC | Optional default schema within that database. |
If you set Database schema, set Database to the database containing it.
5. Test and query
Select Test connection, then Create. Querio tests again before saving. A successful test confirms connectivity, not access to your table.
Follow Connect a datasource to add the intended table to the catalog. Query as a person with datasource permission and exactly one authorized credential. First check the Snowflake identity and context:
SELECT CURRENT_USER(), CURRENT_ROLE(), CURRENT_WAREHOUSE(), CURRENT_DATABASE(), CURRENT_SCHEMA();Check the service user, QUERIO_READER role, and warehouse. Check the database and schema if you set them as defaults. Record two order IDs and their totals from a trusted Snowflake result. Query the same IDs in Querio, replacing 101, 102, and the example object and column names:
SELECT ORDER_ID, ORDER_TOTAL
FROM ANALYTICS.PUBLIC.ORDERS
WHERE ORDER_ID IN (101, 102)
ORDER BY ORDER_ID;Compare the IDs and totals with the trusted result, using the same source data. If a teammate will use this datasource, have them query with their own account. See Groups for credential assignment. Next, add context for the table and check a business answer.
Troubleshooting
| Symptom | Check |
|---|---|
| Connection test fails | Check the account identifier, login name, current public key registered on the service user, and network policy. Ask the administrator to inspect Snowflake diagnostics for the cause. |
| Connection works, table query fails | Confirm the active role has warehouse USAGE, database and schema USAGE, and SELECT on that table or view. Check the object name and casing. |
| Identity or context differs | Check the user's default role and the optional database/schema fields. Querio does not send a separate Snowflake role. |
| One Querio user cannot query | Check their datasource permission and whether exactly one credential is authorized for them. |
After a fix, test the connection and repeat the table query. For connection fields and test behavior, see Datasources and credentials.
Last updated on November 18, 2026