Snowflake

Connect a Snowflake cloud warehouse for federated analysis. Tables are queried through Snowflake and can be joined with datasets from other connectors.

When to use

• Analytics data centralized in Snowflake.
• Combining Snowflake tables with operational databases or object storage in a single analysis.

Before you begin

Prepare a Snowflake user with:

• A role that has read (SELECT) access to the target database and schema, and USAGE on the warehouse.
• A warehouse the role can use to run queries. A small, auto-suspending warehouse is appropriate for interactive analysis.

Prefer a dedicated read-only role scoped to the schemas you will analyze.

Connection settings

Field	Required	Description
Account	Yes	The Snowflake account identifier, e.g. orgname-accountname.
User	Yes	Login name.
Password	Yes	Stored encrypted; never shown after saving.
Warehouse	Yes	The virtual warehouse used to run queries.
Database	Yes	The database to connect.
Schema	Yes	The schema within the database. Defaults to PUBLIC.
Role	—	The role to assume for the session. Set it to a read-only role scoped to the target data.

Test and save

Enter the fields and use Test connection. On success, choose the tables to import.

Capabilities

• Execution model: Federated. Snowflake tables can be joined with datasets from other connectors.
• Access: Read-only. Provide a role limited to SELECT.
• Warehouse cost: Queries consume warehouse credits; an auto-suspending warehouse limits idle cost.

Troubleshooting

• Authentication fails — verify the account identifier format, user, and password.
• Insufficient privileges — ensure the role has USAGE on the warehouse and SELECT on the target schema; set Role explicitly if the user's default role lacks access.
• A table is not visible — grant the role access to its schema and object.

Related

• Connectors overview · BigQuery · MaxCompute