> For the complete documentation index, see [llms.txt](https://docs.zerve.ai/zerve-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerve.ai/zerve-docs/data-and-assets/connections/snowflake.md).

# Snowflake

Connect to Snowflake, with a password or key-pair authentication.

## Connection details

| Field                    | What to enter                                 |
| ------------------------ | --------------------------------------------- |
| **Account name**         | Your Snowflake account identifier             |
| **Warehouse** (optional) | The warehouse to run queries on               |
| **Database**             | The database to connect to                    |
| **Username**             | The user to connect as                        |
| **Authentication**       | A **password**, or a **key pair** (see below) |

## Key-pair authentication

Snowflake connections can use **key-pair authentication** instead of a password. Many organizations prefer it for service accounts, and some require it.

| Field                     | What to enter                                     |
| ------------------------- | ------------------------------------------------- |
| **Private key**           | The private key registered for the Snowflake user |
| **Passphrase** (optional) | The passphrase, if the private key is encrypted   |

Credentials are never shown again after you save them.

## Tips

* Use a **dedicated Snowflake user and role** for Zerve, with access only to what your notebooks need.
* Choose a warehouse sized for the work. Large queries from many parallel runs, such as a [Fleet](/zerve-docs/compute/fleet.md), can use a lot of warehouse capacity.

See [Data connections](/zerve-docs/data-and-assets/connections.md) for creating, naming and attaching connections.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zerve.ai/zerve-docs/data-and-assets/connections/snowflake.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.