Iceberg Tables

Snowflake · Advanced Features

Theory

An Iceberg table in Snowflake stores its data as Parquet files plus Apache Iceberg metadata in cloud storage that you own, connected through an external volume. Snowflake can be the catalog (Snowflake-managed Iceberg tables, with full read and write from Snowflake) or it can read tables whose catalog lives elsewhere, such as AWS Glue, through a catalog integration.

Because the format is open, other engines such as Spark, Flink or Trino can read the same files without copying them into Snowflake. You give up some native features and conveniences in return; for example, storage is billed by your cloud provider and some table features differ from native tables.

Why we use it

Many companies run more than one engine on the same data lake. Iceberg tables let Snowflake work on that shared data while avoiding lock-in to a single storage format and avoiding duplicate copies.

When to use it

Use Iceberg tables when data must be readable by several engines or kept in your own storage in an open format. Use native Snowflake tables when Snowflake is the only engine, since they are simpler and fully managed.

Why an Open Format Matters

Because the underlying files are plain Parquet with an open Iceberg catalog, the exact same table can also be read by Spark, Flink, or Trino — no export step, no vendor lock-in on the data itself, only on where it's cataloged.

What You Give Up vs a Native Table

Iceberg tables support ACID transactions and most standard SQL, but some Snowflake-native conveniences (certain clustering and Time Travel behaviors) work a little differently than on a native permanent table.

When It's the Right Choice

Reach for Iceberg specifically when other engines outside Snowflake genuinely need to read the same physical files — a multi-engine data lake strategy — not as a default replacement for ordinary tables.

How it works

  1. Data must be shared with other engines
  2. Create an external volume on your cloud storage
  3. Should Snowflake manage the Iceberg catalog? Yes: CREATE ICEBERG TABLE with CATALOG = 'SNOWFLAKE'. No: Use a catalog integration to an external catalog.
  4. Query the table with normal SQL in Snowflake
  5. Other engines read the same Parquet and metadata files

Example

CREATE OR REPLACE ICEBERG TABLE lake_events (
  event_id INT, event_type VARCHAR, amount NUMBER(10,2), event_time TIMESTAMP_NTZ(6))
  CATALOG = 'SNOWFLAKE'
  EXTERNAL_VOLUME = 'my_external_volume'
  BASE_LOCATION = 'events_iceberg/';

SELECT * FROM lake_events WHERE event_type = 'purchase';
-- Open format: readable by Spark/Flink/Trino too, full DML, Time Travel works

Key points

Snowflake topics

Snowflake Fundamentals

Warehouses & Performance

Staging & SnowSQL

Tables & Data Handling

Cloud Integrations

Storage & Optimization

Security & Governance

Views, Pipelines & Automation

Data Types & SQL Fundamentals

Semi-Structured Data Deep Dive

Advanced Features

Data Sharing & Collaboration

Cost Management & Monitoring

Databases, Schemas & Objects

Performance Deep Dive

Advanced Security & Governance

Stored Procedures & UDFs

Ecosystem & Integrations

SnowPro Certification Prep

T
Tech Town
Log InSign Up Free
Home SQL Python DSA Power BI Snowflake Databricks Spark Gen AI Practice Problems Contest Blog

Mastering Snowflake

The modern data cloud, from architecture to SnowPro certification. Click any topic in the sidebar to open it right here.

{{ sectionCount }}
Sections
{{ topicCount }}
Topics
Free
Forever
Hands-on practice Practice Snowflake SQL Sharpen the SQL you use in Snowflake: 150 query problems in a live editor with instant checking. Start practising →
Section {{ sec.num }}

{{ sec.label }}

Snowflake  /  {{ current.sectionLabel }}  /  {{ current.name }}

{{ current.name }}

Theory

{{ current.def }}

Why we use it

{{ rich.why }}

When to use it

{{ rich.when }}

{{ sec.h }}

{{ sec.body }}

{{ sec.body }}

Diagram

{{ rich.dg.caption }}

{{ tb.title }}
{{ c.v }}
{{ rich.dg.op }}
➜
{{ rich.dg.output.title }}
{{ c.v }}
{{ nd.label }}
{{ nd.sub }}
{{ nd.label }}
{{ nd.sub }}
{{ rich.dg.left.title }}
{{ it }}
{{ rich.dg.right.title }}
{{ it }}
On screen — where to click

{{ rich.ui.title }}

{{ u.text }}
  1. {{ st.n }}{{ st.text }}
{{ rich.ui.title }}
{{ u.text }}
Flowchart — how it works
{{ nd.text }}
{{ nd.text }}
◇ {{ nd.text }}
Yes → {{ nd.yes }}
No → {{ nd.no }}
Syntax
{{ current.syntax }}
Example
{{ current.example }}
Want to run this yourself? Unlike the SQL and Python courses, Snowflake needs a real account — there's no in-browser engine for it. Click Copy above, then paste it into a free Snowflake trial (30 days, no card required) and run it in Snowsight.
Key Points — click to check off as you learn
  • {{ pt.mark }} {{ pt.text }}

Share this topic