New: Cookbooks and AI ExplanationsStep-by-Step recipes to solve problems connected to Roadmaps and Cheat Sheets. Need more details? Use AI buttons for structured and simple explanations with concrete examples throughout the whole platform.Take a look
Your nightly load already runs late. The business wants today's numbers, not yesterday's.
What you'll have at the end
A pipe watching one storage path that loads new files into the target table within about a minute of arriving, the old nightly job retired, and the pipe's own status and load history there to prove new files are actually landing.
You need
A batch load that already lands cloud storage files into a table on a fixed schedule, using a stage and target table that already work, plus a role able to create pipes, roles and grants in that database.
Not covered
Sub-second, row-by-row streaming ingestion for workloads that can't tolerate even a one-minute delay; that's a separate, heavier mechanism than the file-based pipe this recipe wires up.
Swap streams and tasks for one dynamic table
when the target needs a running merge or aggregation on top of the raw rows, not simply landing them as they arrive, a declarative refresh table replaces the same kind of scheduled-job plumbing this recipe just retired
Is a resource monitor stopping your next runaway Snowflake bill?
once loads run continuously instead of inside one nightly window, a credit cap on the compute behind them is what keeps a stuck or noisy pipe from running up an unwatched bill
Checked 26 Aug 2026
Part of the Snowflake Data Cloud cookbook