QuestionQ16

Ingest and Process Data

A REST API on an on-premises network must be used to ingest data into Snowflake. Due to network restrictions, Snowflake cannot access the data. The data owners propose pushing data to Azure Blob storage every five minutes and running a COPY INTO command, but the Data Engineer is worried about cost. Data transformations will be performed with views after the data is ingested.

Data consumers do not need real-time data, but they expect the data to refresh about every 5 minutes.

Which data-ingestion approach is MOST cost-effective?

Explanation

Bulk loading stages files in Azure Blob Storage and uses COPY INTO <table> to load them into Snowflake. A scheduled five-minute batch load satisfies the stated refresh interval without the continuous, low-latency ingestion infrastructure of Snowpipe Streaming. Snowflake documents Azure Blob Storage as a supported external source for bulk loading with COPY INTO.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!