A company needs to read multiple terabytes of data for an initial load as part of a Snowflake migration. The company can control the number and size of CSV extract files. How does Snowflake…

Question

Options

• AUse auto-ingest Snowpipes to load large files in a serverless model.
• BProduce the largest files possible, reducing the overall number of files to process.
• CProduce a larger number of smaller files and process the ingestion with size Small virtual
• DUse an external tool to issue batched row-by-row inserts within BEGIN TRANSACTION and

• A
  5% (1)
• B
  74% (14)
• C
  5% (1)
• D
  16% (3)

Explanation

Snowflake recommends producing larger files (ideally 100–250 MB compressed) rather than a high volume of tiny files. Each file incurs overhead for parsing, staging, and coordination. When there are too many small files, that metadata and scheduling overhead dominates total load time. Reducing the file count while keeping individual files substantial allows Snowflake's COPY INTO to process them efficiently without excessive per-file overhead. Auto-ingest Snowpipes (A) are designed for continuous, incremental loads-not bulk migrations. Row-by-row inserts (D) are the worst-case pattern for bulk loading performance in any columnar warehouse.

No community discussion yet for this question.