> For the complete documentation index, see [llms.txt](https://integrations.drivetrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.drivetrain.ai/integration-guide/readme/databases-and-warehouses/integrating-with-snowflake.md).

# Integrating with Snowflake

Connect Snowflake to Drivetrain and pipe data warehouse tables into financial planning models. Covers sharing data through a Snowflake Direct Share.

[Prerequisites](#prerequisites)

[Snowflake setup](#snowflake-setup)\
[How to create a share with Drivetrain's account](#how-to-create-a-share-with-drivetrains-account)\
[List of supported Snowflake accounts for direct sharing](#list-of-supported-snowflake-accounts-for-direct-sharing)

## Prerequisites

To connect Snowflake to Drivetrain, you will need:

* Admin privileges in Snowflake

## Snowflake setup <a href="#snowflake-setup" id="snowflake-setup"></a>

**Drivetrain uses Snowflake's Direct Share approach to connect with customer accounts.**\
Direct Shares only work when both accounts are on the **same cloud provider and region**. To support this, we maintain Snowflake accounts across multiple regions and cloud platforms (see list below).

If your account’s provider or region isn’t listed, please reach out—we’ll be happy to set it up for you.

You can read more about Data Sharing via Direct Shares [here](https://docs.snowflake.com/en/user-guide/data-sharing-intro).

### How to create a share with Drivetrain's account

1. Log in to your [Snowflake](https://app.snowflake.com/) account.
2. In the left navigation menu, under **Data Products**, select **Private Sharing**.
3. Click **Share** in the top-right corner and select **Create a Direct Share**.
4. In the **Share Data** dialog, select **+ Select Data** and then:
   1. Select the source database which you want to integrate.
   2. Select the target object or objects from the source database.
   3. Optionally, update the Secure Share Identifier created for your share.
   4. Optionally, enter a Description.
   5. In the remaining text box, enter an account locator. You can find the respective account for your cloud provider and region below. You can only add accounts within the same region to the share. If you don't find any account for your region, please reach out to us.
   6. Select **Create Share**.
5. Share the names of the shares you created, along with your organization details (Organization Name, Account Name, and Locator), with your Customer Success Manager.

### List of supported Snowflake accounts for direct sharing

{% hint style="info" %}
***AWS Snowflake Accounts***<br>

#### **AWS US WEST**

Organization ID: **ICKQIFB**

Account ID: **DRIVETRAIN\_USWEST**

Locator ID: **VJB64118**

Cloud Provider: **AWS**

Region: **US West (Oregon)**

#### **AWS US EAST (Virginia)**

Organization ID: **ICKQIFB**

Account ID: **DRIVETRAIN\_USEAST**

Locator ID: **YIB12816**

Cloud Provider: **AWS**

Region: **US EAST (Virginia)**

#### **AWS US EAST (Ohio)**

Organization ID: **ICKQIFB**

Account ID: **DRIVETRAIN\_USEAST\_OHIO**

Locator ID: **QX73326**

Cloud Provider: **AWS**

Region: **US EAST (Ohio)**

#### **AWS CA CENTRAL (Canada)**

Organization ID: **ICKQIFB**

Account ID: **DRIVETRAIN\_AWS\_CACENTRAL**

Locator ID: **RN48023**

Cloud Provider: **AWS**

Region: **CA CENTRAL (Canada)**

#### **AWS EU CENTRAL (Frankfurt)**

Organization ID: **ICKQIFB**

Account ID: **DRIVETRAIN\_AWS\_EU\_CENTRAL\_1**

Locator ID: **FM31440**

Cloud Provider: **AWS**

Region: **EU CENTRAL 1 (Frankfurt)**
{% endhint %}

{% hint style="info" %}
***GCP Snowflake Accounts***<br>

#### **GCP US CENTRAL (Iowa)**

Organization ID: **ICKQIFB**

Account ID: **DRIVETRAIN\_USCENTRAL**

Locator ID: **AB40701**

Cloud Provider: **GCP**

Region: **US Central (Iowa)**

#### **GCP US EAST (North Virginia)**

Organization ID: **ICKQIFB**

Account ID: **DRIVETRAIN\_GCP\_USEAST4**

Locator ID: **OH55314**

Cloud Provider: **GCP**

Region: **US EAST 4 (North Virginia)**
{% endhint %}

{% hint style="info" %}
***AZURE Snowflake Accounts***<br>

#### **AZURE US WEST (Washington)**

Organization ID: **ICKQIFB**

Account ID: **DRIVETRAIN\_AZ\_USWEST**

Locator ID: **RA27187**

Cloud Provider: **AZURE**

Region: **US West (Washington)**

#### **AZURE CA CENTRAL (Toronto)**

Organization ID: **ICKQIFB**

Account ID: **DRIVETRAIN\_AZURE\_CACENTRAL**

Locator ID: **QN47444**

Cloud Provider: **AZURE**

Region: **Canada Central (Toronto)**

#### **AZURE NORTH EUROPE**

Organization ID: **ICKQIFB**

Account ID: **DRIVETRAIN\_AZURE\_NORTH\_EUROPE**

Locator ID: **LM67628**

Cloud Provider: **AZURE**

Region: **North Europe (Ireland)**

#### **AZURE UK SOUTH (London)**

Organization ID: **ICKQIFB**

Account ID: **DRIVETRAIN\_AZURE\_UKSOUTH**

Locator ID: **OC15986**

Cloud Provider: **AZURE**

Region: **UK South (London)**
{% endhint %}

### Important notes

{% hint style="info" %}
**Important:**

1. Please configure Row Level Security to provide access to relevant tables for Drivetrain. If you’re using a different region on AWS or are on another cloud platform, please share the details with the Drivetrain team.
2. If you encounter any issues while creating a share in Snowflake using the Account ID, please try using the Locator ID instead. If the issue persists, contact your Customer Success Manager or Data Integration Manager for assistance.
   {% endhint %}


---

# 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://integrations.drivetrain.ai/integration-guide/readme/databases-and-warehouses/integrating-with-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.
