MockCertMockCert
Menu

Snowflake conceptsSnowPro CoreData loading

SnowPro Core data loading: COPY, Snowpipe and stages

Match each SnowPro Core data case to its method: external tables, Snowpipe Streaming, dynamic tables or COPY INTO unloading, plus the limits to know.

By MockCert Editorial3 min readPublished Oct 27, 2026 · Updated Nov 1, 2026

An external table reads any format COPY INTO supports except XML. One Snowpipe Streaming channel is capped at 20 MB/s uncompressed by default.

01 Which loading method fits which case?

You know the moment: four ways to move data, and each sounds right. Check this domain's share of the exam, then start from what the data does.

How much of the exam each domain covers

The whole exam

  1. 1.0Snowflake AI Data Cloud Features and Architecture31%
  2. 2.0Account Management and Data Governance20%
  3. 3.0Data Loading, Unloading, and Connectivity18%
  4. 4.0Performance Optimization, Querying, and Transformation21%
  5. 5.0Data Collaboration10%
Data loading sits beside the other domains; weigh your study time to match.

Save the 'How much of the exam each domain covers' graphic as a PNG image PNG for LinkedIn or Pinterest

Which method for which case

  1. Files stay in S3, Azure or GCSExternal table: query in place
  2. Data arrives over SDK channelsSnowpipe Streaming on a pipe
  3. A result must stay freshDynamic table with a target lag
  4. Data has to leave SnowflakeCOPY INTO <location> to files
Find what the data does, then the method follows.

Decide what the data does before you look at the options.

02 What trips people up with external tables?

Once you pick an external table, the details catch you. It reads only external stages and does not inherit the stage's FILE_FORMAT options.

It has no clustering keys, cloning or Time Travel.

External tables need an external stage and their own file format options.

03 What limits does Snowpipe Streaming set?

Streaming has firm rules. With the high-performance architecture, ON_ERROR supports only CONTINUE, and the SDK always uses UTC.

The SDK retries transient errors such as 429 itself, but never reopens an invalid channel. For authorization errors, fix the credential before reopening.

Invalid streaming channels are yours to close and reopen.

04 When is it a dynamic table, or unloading?

Some options are not loading at all. A dynamic table cannot serve data fresher than 60 seconds, its minimum target lag.

COPY INTO unloads to files, gzip-compressed by default; local files are then downloaded with GET. Before your next mock exam, sort your misses into these four cases.

Data fresher than 60 seconds rules out a dynamic table.

Summary

  1. External tables read external stages only, in any COPY format but XML.
  2. A dynamic table's minimum target lag is 60 seconds.

Sources and editorial status

Research checked Nov 1, 2026.

  1. Introduction to external tables | Snowflake Documentation
  2. Limitations and considerations for Snowpipe Streaming with high-performance architecture | Snowflake Documentation
  3. Dynamic tables | Snowflake Documentation
  4. Summary of Data Unloading Features | Snowflake Documentation
  5. CREATE EXTERNAL TABLE | Snowflake Documentation
  6. Error handling in Snowpipe Streaming high-performance architecture | Snowflake Documentation