> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hightouch.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Warehouse Export

> Warehouse Export has your warehouse write query results straight to cloud storage, which Hightouch reads back, so syncs of large models finish faster.

## Overview

A sync normally streams every row of your model's results through Hightouch on its way to the destination. With Warehouse Export, your warehouse writes those results directly into cloud storage instead, and Hightouch reads them back from there. Large models finish faster because the rows take a shorter path.

Your syncs run with or without it. When Warehouse Export isn't available, Hightouch falls back to standard export and the sync delivers the same data to the same destination. Warehouse Export changes how fast a sync runs, not whether it runs.

There's nothing to turn on. Hightouch uses Warehouse Export automatically when your source, your [sync engine](https://docs.hightouch.com/syncs/lightning-sync-engine.md), and your [workspace storage](https://docs.hightouch.com/security/storage.md) all support it, and falls back when they don't.

## Supported sources

Warehouse Export needs your warehouse and your workspace storage to be able to talk to each other, so the storage your workspace uses decides whether it runs.

| Source | Works with storage | What the setup needs |
| - | - | - |
| [Snowflake](https://docs.hightouch.com/sources/snowflake.md#warehouse-export) | Amazon S3, Google Cloud Storage, Azure Blob Storage | Nothing extra for S3. Google Cloud Storage and Azure need a named external stage. |
| [Snowflake Iceberg](https://docs.hightouch.com/sources/snowflake-iceberg.md#warehouse-export) | Amazon S3, Google Cloud Storage, Azure Blob Storage | Same as Snowflake. |
| [Databricks](https://docs.hightouch.com/sources/databricks.md#warehouse-export) | Amazon S3 | A Unity Catalog external location with write access to the bucket. |
| [BigQuery](https://docs.hightouch.com/sources/google-bigquery.md#warehouse-export) | Google Cloud Storage | The BigQuery service account must be able to write to the bucket. |
| [Amazon Redshift](https://docs.hightouch.com/sources/amazon-redshift.md#warehouse-export) | Amazon S3 | A network route from the cluster to S3. |
| [Amazon Athena](https://docs.hightouch.com/sources/amazon-athena.md#warehouse-export) | Amazon S3 | A query output location, on the workgroup or on the source. |

Each source page covers its own requirements in full. If your source isn't listed, your syncs use standard export.

## When Hightouch stops using Warehouse Export

Hightouch stops using Warehouse Export for a sync when it hits a problem, and how it responds depends on whether the problem looks fixable.

### A configuration problem

Something in your warehouse or storage setup prevents the export: a missing external location, a storage integration without the right grants, a bucket the warehouse can't write to. Retrying won't help until you change the configuration, so Hightouch stops using Warehouse Export for the affected syncs rather than attempting it on every run.

The sync's overview and the source's configuration page both show that Hightouch isn't using Warehouse Export, along with what went wrong. The syncs keep running on standard export in the meantime. Once you've fixed the underlying problem, re-enable Warehouse Export and Hightouch uses it again on the next run.

### A one-off problem on a single run

Some failures are specific to one run's data, such as a row that exceeds the size limit your warehouse allows for an export. These aren't configuration problems, so Hightouch doesn't stop using Warehouse Export. That run falls back to standard export, the run summary says so, and the next run attempts Warehouse Export again. You don't need to do anything.

## Re-enable Warehouse Export

After you've fixed a configuration problem, tell Hightouch to try again. Nothing re-enables on its own, because Hightouch can't tell from the outside that your warehouse or storage changed.

To re-enable it for one sync, open the sync and select **Re-enable** next to its Warehouse Export status. You can do the same from a run's summary page.

To re-enable it for every affected sync on a source at once, go to the source, open the **Configuration** tab, and select **Re-enable all syncs**.

Hightouch checks that Warehouse Export works before clearing anything. If the original problem is still there, nothing changes and the message says what's still wrong. You need permission to edit the sync, or the source, to re-enable it.

## Next steps

* [Lightning sync engine](https://docs.hightouch.com/syncs/lightning-sync-engine.md) to see which engine your source runs and what it changes about a sync.
* [Storage](https://docs.hightouch.com/security/storage.md) to configure your workspace to export to your own cloud storage bucket.
* [Warehouse sync logs](https://docs.hightouch.com/syncs/warehouse-sync-logs.md) to write each sync's results back to your warehouse.