Loading from S3, Azure Blob, GCS in Snowflake - Time & Space Complexity

Time Complexity: Loading from S3, Azure Blob, GCS

O(n)

Understanding Time Complexity

When loading data from cloud storage like S3, Azure Blob, or GCS into Snowflake, it's important to understand how the time taken grows as the data size increases.

We want to know how the number of operations changes when we load more files or bigger files.

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

COPY INTO my_table
FROM @my_stage
FILE_FORMAT = (TYPE = 'CSV')
PATTERN = '.*\\.csv'
ON_ERROR = 'CONTINUE';
    

This command loads all CSV files from a cloud storage stage into a Snowflake table.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: Reading each file from cloud storage (S3, Azure Blob, or GCS) and loading it into Snowflake.
• How many times: Once per file in the stage matching the pattern.

How Execution Grows With Input

As the number of files increases, Snowflake makes one read operation per file to load the data.

Input Size (n files)	Approx. API Calls/Operations
10	About 10 file read operations
100	About 100 file read operations
1000	About 1000 file read operations

Pattern observation: The number of operations grows directly with the number of files to load.

Final Time Complexity

Time Complexity: O(n)

This means the time to load data grows linearly with the number of files being loaded.

Common Mistake

[X] Wrong: "Loading many small files is just as fast as loading one big file of the same total size."

[OK] Correct: Each file requires a separate read operation, so many small files cause more overhead and take longer than one big file.

Interview Connect

Understanding how loading scales with file count helps you design efficient data pipelines and shows you can think about real-world cloud data workflows.

Self-Check

"What if we compressed all files into one archive file before loading? How would the time complexity change?"

Practice

1. What is the main purpose of using COPY INTO in Snowflake when loading data from S3, Azure Blob, or GCS?

easy

A. To load data files from cloud storage into Snowflake tables

B. To export data from Snowflake to cloud storage

C. To create a new cloud storage bucket

D. To delete files from cloud storage

Solution

1. Step 1: Understand the role of COPY INTO

   The COPY INTO command is used in Snowflake to load data from external cloud storage into Snowflake tables.

2. Step 2: Differentiate from other operations

   Exporting data, creating buckets, or deleting files are not done by COPY INTO. It specifically loads data into tables.

3. Final Answer:

   To load data files from cloud storage into Snowflake tables -> Option A

4. Quick Check:

   Loading data = COPY INTO [OK]

Hint: COPY INTO loads data from cloud storage to tables [OK]

Common Mistakes:

• Confusing COPY INTO with export commands
• Thinking COPY INTO manages cloud storage buckets
• Assuming COPY INTO deletes files

2. Which of the following is the correct syntax to load data from an S3 bucket into a Snowflake table named my_table?

easy

A. COPY INTO my_table FROM @my_s3_stage FILE_FORMAT = (TYPE = 'CSV');

B. LOAD DATA INTO my_table FROM 's3://mybucket/data.csv';

C. INSERT INTO my_table SELECT * FROM s3://mybucket/data.csv;

D. IMPORT INTO my_table FROM @my_s3_stage FORMAT = CSV;

Solution

1. Step 1: Identify correct Snowflake COPY INTO syntax

   Snowflake uses COPY INTO table_name FROM @stage FILE_FORMAT = (TYPE = 'format') to load data.

2. Step 2: Eliminate incorrect options

   LOAD DATA INTO is not valid Snowflake syntax. Direct INSERT INTO ... FROM s3:// paths are not supported. IMPORT INTO does not exist. The correct syntax is COPY INTO my_table FROM @my_s3_stage FILE_FORMAT = (TYPE = 'CSV');.

3. Final Answer:

   COPY INTO my_table FROM @my_s3_stage FILE_FORMAT = (TYPE = 'CSV'); -> Option A

4. Quick Check:

   COPY INTO + stage + file format = correct syntax [OK]

Hint: COPY INTO + @stage + FILE_FORMAT is the right pattern [OK]

Common Mistakes:

• Using LOAD DATA instead of COPY INTO
• Trying to SELECT directly from S3 path
• Using IMPORT INTO which is invalid

3. Given the following Snowflake command:

COPY INTO sales FROM @azure_blob_stage FILE_FORMAT = (TYPE = 'JSON') ON_ERROR = 'CONTINUE';

What happens if one file in the Azure Blob storage has invalid JSON data?

medium

A. The entire load fails and no data is loaded

B. Snowflake automatically fixes the invalid JSON and loads all data

C. Only the invalid file is skipped, and loading continues for others

D. The command ignores the error and loads all files including invalid data

Solution

1. Step 1: Understand ON_ERROR = 'CONTINUE'

   This option tells Snowflake to skip files or rows with errors and continue loading the rest.

2. Step 2: Apply to invalid JSON file

   The invalid JSON file will be skipped, but other valid files will load successfully.

3. Final Answer:

   Only the invalid file is skipped, and loading continues for others -> Option C

4. Quick Check:

   ON_ERROR = CONTINUE skips errors, loads rest [OK]

Hint: ON_ERROR = CONTINUE skips bad files, loads others [OK]

Common Mistakes:

• Assuming entire load fails on one bad file
• Thinking Snowflake auto-fixes JSON errors
• Believing invalid data is loaded anyway

4. You run this command to load data from Google Cloud Storage:

COPY INTO customers FROM @gcs_stage FILE_FORMAT = (TYPE = 'CSV');

But you get an error saying 'Storage integration not authorized'. What is the most likely cause?

medium

A. The GCS bucket is empty

B. The CSV file format is incorrect

C. The Snowflake table does not exist

D. The storage integration lacks permission to access the GCS bucket

Solution

1. Step 1: Analyze the error message

   'Storage integration not authorized' means Snowflake cannot access the cloud storage due to permission issues.

2. Step 2: Identify cause

   The storage integration must have proper permissions to read from the GCS bucket. Other options do not cause authorization errors.

3. Final Answer:

   The storage integration lacks permission to access the GCS bucket -> Option D

4. Quick Check:

   Authorization error = permission issue [OK]

Hint: Authorization errors usually mean permission problems [OK]

Common Mistakes:

• Blaming file format for authorization errors
• Assuming table existence causes storage errors
• Ignoring permission setup for storage integration

5. You want to load multiple CSV files from an S3 bucket into Snowflake, but only files with the prefix 2024/. Which COPY INTO command correctly filters these files?

hard

A. COPY INTO sales FROM @s3_stage FILE_FORMAT = (TYPE = 'CSV') WHERE filename LIKE '2024/%';

B. COPY INTO sales FROM @s3_stage FILE_FORMAT = (TYPE = 'CSV') PATTERN = '^2024/.*';

C. COPY INTO sales FROM @s3_stage FILE_FORMAT = (TYPE = 'CSV') FILES = ('2024/');

D. COPY INTO sales FROM @s3_stage FILE_FORMAT = (TYPE = 'CSV') PATTERN = '2024/.*';

Solution

1. Step 1: Understand file filtering in COPY INTO

   Snowflake uses the PATTERN parameter with a regular expression to filter files by name or prefix.

2. Step 2: Check regex correctness

   PATTERN = '^2024/.*' matches files starting exactly with '2024/'. PATTERN = '2024/.*' without the ^ may match files where '2024/' appears elsewhere in the path. The other options use invalid parameters like WHERE or FILES.

3. Final Answer:

   COPY INTO sales FROM @s3_stage FILE_FORMAT = (TYPE = 'CSV') PATTERN = '^2024/.*'; -> Option B

4. Quick Check:

   PATTERN with ^ prefix filters files correctly [OK]

Hint: Use PATTERN with ^ prefix to filter file names [OK]

Common Mistakes:

• Omitting ^ in regex causing wrong files to load
• Using WHERE or FILES incorrectly for filtering
• Confusing file prefix with file list