Swap streams and tasks for one dynamic table

A stream, a task, and a MERGE statement keep one summary table caught up, and every schedule tweak means editing all three.

Intermediate to advancedRead 9 minDoing: an afternoon8 steps

▶ Start

What you'll have at the end

One dynamic table that replaces the stream, the task, and the manual sync step, refreshing itself on its own schedule

Before you start

You need

A working pipeline where a stream on a base table, a scheduled task, and a MERGE statement together keep one summary table current, plus a role able to create dynamic tables and warehouses in the same database.

Not covered

A MERGE that does running totals, soft deletes, or joins against the stream itself, logic a single query can't express; that needs a heavier, custom incremental rewrite instead, a different tool for a narrower case.

Leans on

8 steps

Where to go next

Give a new Snowflake warehouse an auto-suspend before it idles

the warehouse this table refreshes on still idles up to its default timeout between refreshes unless you set that separately

Checked 26 Aug 2026

Part of the Snowflake Data Cloud cookbook