Practical, sourced guides to building and running data platforms on Snowflake: warehouses, cost control, governance, and the agent and AI features data teams actually ship.
Snowflake tag-based data protection policies entered public preview on July 21, 2026, letting you attach row access, aggregation, projection, and join policies to tags. Objects with the tag auto-inherit the policy, cutting policy attachments from thousands to one per group.
With GA workload identity federation, Snowflake acts as an OIDC provider so workloads use short-lived tokens instead of static credentials, at no extra cost.
Dynamic Iceberg table replication now keeps Snowflake managed Iceberg pipelines in DR plans, but refresh and transfer costs move to the target account.
GA on AWS in six regions, Snowflake Adaptive Compute brings query-level billing and a 1.2x benchmark edge over Gen2 warehouses.
Snowflake Dynamic Tables now claim up to 2.8x faster refresh on Gen2 warehouses, but the cost win depends on target lag and change volume.
Row-store Snowflake Hybrid Tables handle OLTP-style work, and new preview optimizations report up to 8 times the throughput.
Azure teams can now read and write externally managed Iceberg tables in Snowflake without moving storage, through GA ADLS support.
Set to AUTO, Snowflake's GA ICEBERG_MERGE_ON_READ_BEHAVIOR switch sends 3 of 4 Iceberg table cases to merge-on-read.
Cortex Agents let you build an AI agent that reasons across structured tables, unstructured documents, and custom tools inside Snowflake. It orchestrates a plan-act-reflect loop, and the bill is the sum of four meters you need to watch.
Snowflake Cortex AI exposes LLMs as SQL functions like AI_COMPLETE and AI_CLASSIFY, so you run inference without moving data out. It is billed per token by model, and cost swings roughly 40x between a small model and a frontier one, so model choice is the budget.
Business users ask questions in plain English and get SQL answers with Cortex Analyst. Accuracy depends on your semantic view; billing is per message.
Snowflake's Cortex Search runs managed hybrid search for RAG without a vector database, but its several meters bill serving compute even when idle.
Snowflake Gen2 standard warehouses run on faster hardware and finish most queries quicker, but they bill at a higher credit rate and you often have to switch with a SQL clause. Whether they save money depends entirely on whether the speedup beats the rate.
Granting privileges to roles instead of users collapses thousands of Snowflake grants to a few hundred, and one masking policy protects many columns.
Snowflake Iceberg tables store data in open Apache Iceberg format in your own cloud storage, so Snowflake bills zero storage and other engines can read it. The catch: only Snowflake-managed catalog tables get full platform support, external-catalog tables lose clustering, cloning, and replication.
Built on Apache NiFi, Snowflake Openflow moves data from any source into Snowflake, running inside Snowflake or in your own VPC, each billed differently.
Snowflake clustering keys reorganize micro-partitions so queries prune more of the table. On a well-clustered date column a one-day query can scan 140 micro-partitions instead of 9,800, but automatic clustering bills credits, so it only pays on big, filtered, slow-changing tables.
Dynamic Tables let you declare a SELECT and a target lag and let Snowflake refresh it; Streams and Tasks give you imperative control. Dynamic Tables bottom out at a 60-second minimum lag, so sub-minute freshness still means Snowpipe Streaming or Tasks.
Snowflake warehouse sizing sets your credit burn: each size up doubles credits per hour, so a 4XL costs 128 credits per hour against an XS at 1. Right-size by workload, not by habit.
The Snowflake section exists because most Snowflake writing falls into two camps: vendor marketing that announces a feature, and documentation that explains the syntax. What is missing in between is the operator's question: what does this change do to my bill, my pipelines, and my access model on Monday morning?
Each guide starts from a primary source. The Engineering Desk watches the Snowflake release notes, the Snowflake engineering blog, and the product documentation once a week, and drafts a guide only when a release changes something a data team actually runs: warehouse sizing, credit consumption, Cortex and agent features, Iceberg tables, governance and RBAC, or Openflow ingestion.
The responsible editor, Lars Cornelissen, runs Snowflake in production as a data engineer at Alliander. That is where the cost and governance angles come from, and when a guide draws on that work it says so in an editor's note rather than dressing it up as a general claim.
What you will find here:
What you will not find: rewritten press releases, or a guide for every release note. Many weeks ship nothing that changes how a team works, and those weeks produce no guide.
The filters above group the guides by topic. Every guide links to the documentation it relies on, and corrections are logged on the corrections page.
From the Data Today newsroom
These guides are part of Data Today. Read the wider data & AI coverage on the main site.
Go to Data Today