External Tables
In shortAn external table lets you query files in an external stage as a read-only table, without loading them. Snowflake stores only metadata about the files.
- Source
- Files in an external stage (your or a partner's bucket)
- Trigger
- A query; new files appear after a metadata refresh (event notification or manual)
- Processor
- Your warehouse, which reads the files at query time
- Destination
- None: results only, nothing is loaded
- Compute and billing
- Warehouse credits per query; automatic file registration has a small serverless cost; the files are billed by your cloud provider
The problem
A logistics partner writes Parquet files into its own S3 bucket every night, and the contract says the data stays there. IsmaFrost still wants to query it with SQL.
How it works
PARTNER'S BUCKET · FILES STAY THERE
CLOUD EVENTNew file arrivedtriggers AUTO_
FILESParquet filesdate=2026-10-25/
ISMAFROST ACCOUNT
EXTERNAL TABLEEXT_
files
COMPUTEWarehousereads the files at query time
MATERIALIZED VIEWHot slicestored in Snowflake (optional)
Every row exposes a VALUE VARIANT column with the record. The other columns are expressions over VALUE or over the file path. A partition column is an expression on METADATA$FILENAME, and filtering on it lets Snowflake skip whole folders, which is the main performance lever.
Example: last night's deliveries
-- Files are laid out as date=YYYY-MM-DD/ part-0. parquet under the stage path CREATE EXTERNAL TABLE sales_db. raw. ext_ deliveries ( delivery_date DATE AS TO_ DATE( SPLIT_ PART( SPLIT_ PART( METADATA$FILENAME, 'date=', 2), '/', 1)), shipment_id STRING AS (VALUE: shipment_ id: : STRING), weight_kg NUMBER AS (VALUE: weight_ kg: : NUMBER) )PARTITION BY (delivery_ date) LOCATION = @sales_db. raw. partner_ stage/ FILE_FORMAT = (TYPE = PARQUET)AUTO_REFRESH = TRUE;ALTER EXTERNAL TABLE sales_db. raw. ext_ deliveries REFRESH; -- manual refresh when no events SELECT delivery_date, COUNT(*), SUM( weight_ kg) FROM sales_db. raw. ext_ deliveries WHERE delivery_date = '2026-10-26' -- prunes to one folder GROUP BY delivery_date;
Expected resultAlice gets one row for 26 October. Only the files under date=2026-10-26/ are read, because the filter is on the partition column.
- Read-only: no INSERT, UPDATE or DELETE.
- No Time Travel or Fail-safe: the files aren't in Snowflake storage.
- New files stay invisible until the metadata is refreshed.
Which option to use
External table
The files must stay in place and are queried occasionally. Add a materialized view (Enterprise) for a hot slice.
Load into a table
The data is queried heavily and repeatedly. Native tables prune better and get Time Travel.
Iceberg table (Part 6)
You need writes, or other engines must share the same open-format table. For heavy queries on Parquet, Snowflake recommends Iceberg over external tables.
- External table = metadata in Snowflake, data in your bucket, read-only.
- Refresh metadata (automatically through events, or manually) to see new files.
- No Time Travel, no Fail-safe, no Snowflake storage charge for the files.

