Why Stages (internal and external) in Snowflake? - Purpose & Use Cases

The Big Idea

What if you could stop juggling files and let Snowflake handle your data loading smoothly?

The Scenario

Imagine you have many files to load into your Snowflake database. You try to upload each file manually from your computer every time you want to update your data.

The Problem

This manual uploading is slow and tiring. You might forget to upload some files or upload wrong versions. It's hard to keep track of what's been loaded and what hasn't.

The Solution

Snowflake stages let you store files in one place, either inside Snowflake (internal) or outside like cloud storage (external). You can load data easily from these stages without manual uploads every time.

Before vs After

✗ Before

PUT file://data.csv @mytable;
COPY INTO mytable FROM @mytable;

✓ After

COPY INTO mytable FROM @mystage/data.csv;

What It Enables

It makes loading and managing data files fast, reliable, and repeatable without manual file handling.

Real Life Example

A company regularly uploads sales data files to an external cloud storage stage. Snowflake automatically loads these files into tables daily without manual work.

Key Takeaways

Manual file uploads are slow and error-prone.

Stages store files inside or outside Snowflake for easy access.

Using stages automates and speeds up data loading.

Practice

1. What is the main difference between an internal stage and an external stage in Snowflake?

easy

A. Internal stages store files inside Snowflake, external stages link to cloud storage.

B. Internal stages are only for unloading data, external stages are only for loading data.

C. Internal stages require a file format, external stages do not.

D. Internal stages are free, external stages always cost extra.

Solution

1. Step 1: Understand internal stage storage

   Internal stages keep files physically inside Snowflake's managed storage.

2. Step 2: Understand external stage storage

   External stages point to external cloud storage like AWS S3 or Azure Blob.

3. Final Answer:

   Internal stages store files inside Snowflake, external stages link to cloud storage. -> Option A

4. Quick Check:

   Internal vs external storage location = A [OK]

Hint: Remember: internal = inside Snowflake, external = outside Snowflake [OK]

Common Mistakes:

• Thinking internal stages can link to external cloud storage
• Confusing loading and unloading roles of stages
• Assuming file format is only needed for internal stages

2. Which of the following is the correct syntax to create an internal stage named mystage in Snowflake?

easy

A. CREATE STAGE mystage URL='s3://mybucket/data/';

B. CREATE STAGE mystage FILE_FORMAT = (TYPE = 'CSV');

C. CREATE EXTERNAL STAGE mystage FILE_FORMAT = (TYPE = 'CSV');

D. CREATE STAGE mystage STORAGE_INTEGRATION = my_integration;

Solution

1. Step 1: Identify internal stage syntax

   Internal stages do not require URL or STORAGE_INTEGRATION parameters.

2. Step 2: Check file format usage

   Specifying FILE_FORMAT is valid and common for internal stages.

3. Final Answer:

   CREATE STAGE mystage FILE_FORMAT = (TYPE = 'CSV'); -> Option B

4. Quick Check:

   Internal stage creation syntax = B [OK]

Hint: Internal stage needs FILE_FORMAT, no URL or integration [OK]

Common Mistakes:

• Using URL parameter for internal stages
• Confusing external stage syntax with internal
• Omitting FILE_FORMAT when needed

3. Given this Snowflake SQL snippet:

CREATE OR REPLACE STAGE ext_stage
URL='s3://mybucket/data/'
STORAGE_INTEGRATION = my_int
FILE_FORMAT = (TYPE = 'JSON');

LIST @ext_stage;

What will the LIST @ext_stage; command do?

medium

A. List files stored inside Snowflake internal stage named ext_stage.

B. Return an error because FILE_FORMAT is not allowed in stage creation.

C. Show the contents of the JSON files in the stage.

D. List files in the external S3 bucket linked by ext_stage.

Solution

1. Step 1: Identify stage type from syntax

   URL and STORAGE_INTEGRATION indicate an external stage linked to S3.

2. Step 2: Understand LIST command behavior

   LIST @stage lists files in the stage's storage location, here the S3 bucket.

3. Final Answer:

   List files in the external S3 bucket linked by ext_stage. -> Option D

4. Quick Check:

   LIST on external stage lists external files = C [OK]

Hint: LIST @stage shows files where stage points, internal or external [OK]

Common Mistakes:

• Thinking LIST shows file contents, not file names
• Assuming FILE_FORMAT is invalid in stage creation
• Confusing internal and external stage storage

4. You try to create an external stage with this command:

CREATE STAGE mystage
URL='s3://mybucket/data/';

But get an error. What is the most likely cause?

medium

A. Missing STORAGE_INTEGRATION for external stage access.

B. FILE_FORMAT is required for external stages.

C. Internal stages cannot use URL parameter.

D. Stage name mystage is reserved.

Solution

1. Step 1: Check external stage requirements

   External stages need STORAGE_INTEGRATION to access cloud storage securely.

2. Step 2: Identify missing parameter

   The command lacks STORAGE_INTEGRATION, causing access error.

3. Final Answer:

   Missing STORAGE_INTEGRATION for external stage access. -> Option A

4. Quick Check:

   External stage needs integration = D [OK]

Hint: External stage always needs STORAGE_INTEGRATION for cloud access [OK]

Common Mistakes:

• Assuming FILE_FORMAT is mandatory for external stage creation
• Confusing internal stage syntax with external
• Thinking stage name causes error

5. You want to unload query results to a stage and then copy them to an external S3 bucket. Which setup is best practice?

hard

A. Unload to local machine, then upload manually to S3 external stage.

B. Unload directly to an external stage linked to S3, then copy from there.

C. Unload to an internal stage, then use Snowflake commands to copy to external stage.

D. Unload to internal stage and keep data only there without copying.

Solution

1. Step 1: Understand unloading to stages

   Unloading query results to internal stage is fast and secure inside Snowflake.

2. Step 2: Copying to external storage

   Use Snowflake COPY INTO command to move data from internal to external stage.

3. Step 3: Evaluate other options

   Direct unload to external stage is possible but less controlled; manual upload is inefficient.

4. Final Answer:

   Unload to an internal stage, then use Snowflake commands to copy to external stage. -> Option C

5. Quick Check:

   Unload internal then copy external = A [OK]

Hint: Unload inside Snowflake first, then copy out [OK]

Common Mistakes:

• Unloading directly to external stage without integration setup
• Manual upload instead of automated copy
• Not copying data out after unloading