> For the complete documentation index, see [llms.txt](https://datalab-docs.datacamp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://datalab-docs.datacamp.com/connect-to-data/snowflake.md). # Snowflake ## Set up a Snowflake connection When inside a workbook, click **View** > **Databases**, then click the **+** icon and follow the on-screen instructions. To find your account name, follow [these instructions](https://docs.snowflake.com/en/user-guide/admin-account-identifier). Note that in some cases, it's necessary to [include your cloud region in the identifier](https://docs.snowflake.com/en/user-guide/admin-account-identifier#format-2-legacy-account-locator-in-a-region).

For detailed instructions, see [Connect your data to DataLab](/connect-to-data/connect-your-data-to-workspace.md). If you want to experiment with Snowflake without setting up a connection, you can use our sample data warehouse with London Public Transit data. ## Query the database You can now query the Snowflake data warehouse with a [SQL cell](/work/sql-cell.md). Select it in the **Select source** dropdown in the top left corner of a SQL cell, or select the sample Snowflake database.

Example of a SQL cell using the `London Public Transport` connection. The query result is available as `TFL_JOURNEYS`.

--- # 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://datalab-docs.datacamp.com/connect-to-data/snowflake.md?ask=&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.