Snowflake: A Warehouse That Splits Storage From Compute
The one architectural idea behind Snowflake — and why pulling storage apart from compute changes how you think about a data warehouse.
A cloud data warehouse from first principles — Snowsight, virtual warehouses, loading, roles, time travel, semi-structured data, clustering and performance, cost governance, data sharing, and programmability.
The one architectural idea behind Snowflake — and why pulling storage apart from compute changes how you think about a data warehouse.
Sign up for a free trial, find your way around Snowsight, and get a real query result back before you've read to the bottom of the page.
Snowflake's object hierarchy is ordinary until you hit the word 'warehouse' — which means compute, not storage. Here's the model, and the trap, cleared up.
Snowflake ships a million-order business you can query on day one — TPCH — so you can learn joins, window functions, the Query Profile, and warehouse behavior before loading a single row of your own.
In Snowflake, files don't go straight into tables — they land in a stage first, then COPY INTO loads them. Here's the model, the click-through wizard, and the SQL path that scales.
COPY INTO is a batch verb — somebody has to decide when to run it. This chapter is about deleting that somebody: Snowpipe's auto-ingest wiring, Snowpipe Streaming's row-based path, the file-size tax that quietly bills you, and the unload direction that hands data back to the rest of the world.
The trial hands you ACCOUNTADMIN and it's tempting to never leave. Here's Snowflake's role model, the system roles, the functional/access-role pattern, and the grants that keep access sane once it's not just you.
In Snowflake you don't rent a server, you buy compute-seconds — which means cost is something you design, and a warehouse left running is money on fire.
Two Snowflake features that feel like sorcery — querying the past and copying a database for free — turn out to be the same storage trick wearing two hats.
Everything the series taught, pointed at one target: a real analysis of a million-order business, from setting context to answering questions a stakeholder would actually ask.
VARIANT, OBJECT, ARRAY, JSON loading, path navigation, FLATTEN, and why semi-structured support is a first-class warehouse feature.
Permanent, transient, temporary, external, Iceberg, and dynamic tables; standard, materialized, and secure views.
Pruning, clustering keys, search optimization, query profile, explain plans, spilling, and Snowflake cache layers.
The credit model, cloud-services charges, warehouse metering, account usage views, statement timeouts, and the controls that stop surprise bills.
Secure Data Sharing, reader accounts, listings, and why sharing is a core Snowflake primitive rather than an export job.
Dynamic data masking, row access policies, and tag-based governance — the Enterprise features that decide which rows and which column values a role actually sees, long after RBAC has said yes.
The orientation chapter for writing code near Snowflake data without turning the warehouse into an application server.
SnowSQL, Snowflake CLI, Python/JDBC/ODBC drivers, key-pair auth, MFA, network policies, and the setup needed before tools integrate.
Identifier case, QUALIFY, timestamp variants, NUMBER precision, GEOGRAPHY, PIVOT, and the syntax details that prevent subtle portability bugs.
Organizations, account locators, roles, users, network policies, INFORMATION_SCHEMA, SHOW, DESCRIBE, and the DDL lifecycle.