> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/connectors/partner-types/data-warehouse.md).

# Data warehouse

Connecting a cloud data warehouse to mediarithmics, and why it belongs to a different phase of the integration.

Every other partner type on this list is about getting data **out** of mediarithmics. This one is about connecting mediarithmics to the warehouse where the rest of your data already lives.

That difference is not only directional. A warehouse connection is set up at a different point in a project - usually during the initial integration, alongside the data model - and by different people. It is infrastructure, not activation, which is why these connectors live under [Sources](/connectors/sources/google-bigquery.md) rather than alongside the feeds.

## Connectors

<table data-search="false"><thead><tr><th width="300">Connector</th><th></th></tr></thead><tbody><tr><td><a href="/connectors/sources/google-bigquery.md">Google BigQuery</a></td><td>Authenticates with a dedicated service account and a credentials JSON file.</td></tr><tr><td><a href="/connectors/sources/snowflake.md">Snowflake</a></td><td>Authenticates with a key pair on a dedicated service user - not a password.</td></tr></tbody></table>

{% hint style="info" %}
The data warehouse feature is in Alpha. Contact your account manager to learn more.
{% endhint %}

## What these connections need

Both follow the same shape, and both grant mediarithmics **read-only access by default**:

* A **dedicated service account or user**, rather than a personal one.
* **Read access** to the data you want to expose, which can be narrowed from the whole project down to specific tables.
* A **working schema** with write access - but only if your synchronisation strategy handles updates and deletes. If it does not, skip it and keep the connection read-only.
* A **credentials file** in the format the provider expects.

The full procedure for each provider - roles, grant scripts, key generation, credential formats - is documented in the **Setup & Monitor** section, under *Collect & manage your data › Sync with your data warehouse › Warehouse compatibilities*. The connector pages here are entry points to it, not a second copy.

## Related types

For sending mediarithmics data **out** to a file destination rather than reading from a warehouse, see [Data sharing & export](/connectors/partner-types/data-sharing-and-export.md).


---

# 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.mediarithmics.io/connectors/partner-types/data-warehouse.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.