Snowflakeにおけるデータパイプラインの自動化
Emily Melhuish
Technical Curriculum Developer, Snowflake
ダイナミックテーブル:

ストリームとタスク:

宣言的パイプライン自動化
SELECT クエリで内容を定義 — 結果を記述するだけで、Snowflakeが更新を管理CREATE DYNAMIC TABLE logistics.delivery_summary
TARGET_LAG = '1 hour'
WAREHOUSE = harbr_wh
AS
SELECT region, COUNT(*) AS shipments,
AVG(delivery_days) AS avg_days
FROM logistics.shipments GROUP BY region;
ユーザーとSnowflake間の鮮度の契約
| TARGET_LAG 値 | 効果 |
|---|---|
'5 minutes' |
最大5分の遅延 — 頻繁に更新 |
'1 hour' |
更新頻度が低い — コンピューティング消費を削減 |
DOWNSTREAM |
下流の依存関係からラグを推定 — テーブル連鎖に最適 |
増分更新
-- Incremental-friendly:
SELECT region, COUNT(*) AS shipments
FROM logistics.shipments
GROUP BY region;
完全更新

DOWNSTREAM ラグは次のテーブルのニーズに従い、過剰更新を防止ダイナミックテーブル: 宣言的
-- Declare the result for Snowflake
CREATE DYNAMIC TABLE logistics.summary
TARGET_LAG = '1 hour'
WAREHOUSE = harbr_wh
AS SELECT region, COUNT(*)
FROM shipments
GROUP BY 1;
ストリーム+タスク: 命令的
-- You control every step
CREATE TASK process_events
SCHEDULE = '5 MINUTE'
WHEN SYSTEM$STREAM_HAS_DATA
('events_stream')
AS CALL logistics.process_new_events();
SELECT name, state, refresh_start_time, refresh_end_time
FROM TABLE (
INFORMATION_SCHEMA.DYNAMIC_TABLE_REFRESH_HISTORY (
NAME_PREFIX => 'HARBR_DB.DELIVERY_SUMMARY.', ERROR_ONLY => TRUE
)
)
ORDER BY name, data_timestamp;
| NAME | TRIGGER | STATE | START | END |
|---|---|---|---|---|
| DELIVERY_SUMMARY | SCHEDULED | SUCCEEDED | 2026-03-01 05:00:00 | 2024-03-01 05:00:08 |
| DELIVERY_SUMMARY | SCHEDULED | FAILED | 2026-03-01 04:00:00 | 2024-03-01 04:00:03 |
Snowflakeにおけるデータパイプラインの自動化