Creating tables (permanent, temporary, transient) in Snowflake - Performance & Efficiency

Time Complexity: Creating tables (permanent, temporary, transient)

O(n)

Understanding Time Complexity

When creating tables in Snowflake, it is important to understand how the time taken grows as you create more tables.

We want to know how the number of operations changes when creating many tables.

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

-- Create a permanent table
CREATE TABLE my_permanent_table (id INT, name STRING);

-- Create a temporary table
CREATE TEMPORARY TABLE my_temp_table (id INT, name STRING);

-- Create a transient table
CREATE TRANSIENT TABLE my_transient_table (id INT, name STRING);

-- Repeat creation for multiple tables
DECLARE i INT DEFAULT 1;
WHILE i <= 100 DO
  EXECUTE IMMEDIATE 'CREATE TABLE table_' || i || ' (id INT, value STRING)';
  LET i = i + 1;
END WHILE;

This sequence creates different types of tables and then creates many tables in a loop.

Identify Repeating Operations

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

• Primary operation: The CREATE TABLE command executed once per table.
• How many times: Once for each table created, for example 100 times in the loop.

How Execution Grows With Input

Each new table requires a separate CREATE TABLE operation, so the total work grows as you create more tables.

Input Size (n)	Approx. Api Calls/Operations
10	10 CREATE TABLE commands
100	100 CREATE TABLE commands
1000	1000 CREATE TABLE commands

Pattern observation: The number of operations grows directly with the number of tables created.

Final Time Complexity

Time Complexity: O(n)

This means the time to create tables grows in a straight line as you create more tables.

Common Mistake

[X] Wrong: "Creating multiple tables happens all at once, so time stays the same no matter how many tables."

[OK] Correct: Each CREATE TABLE is a separate operation that takes time, so more tables mean more total time.

Interview Connect

Understanding how operations scale helps you design efficient database setups and shows you can think about system behavior as it grows.

Self-Check

"What if we created tables in parallel instead of one after another? How would the time complexity change?"

Practice

1. Which type of table in Snowflake is best suited for storing data that needs to persist permanently and be recoverable after accidental deletion?

easy

A. TEMPORARY table

B. PERMANENT table

C. TRANSIENT table

D. EXTERNAL table

Solution

1. Step 1: Understand table types in Snowflake

   Permanent tables store data permanently and include fail-safe for recovery.

2. Step 2: Compare with other table types

   Temporary tables last only for the session, and transient tables do not have fail-safe, so they are not recoverable after deletion.

3. Final Answer:

   PERMANENT table -> Option B

4. Quick Check:

   Permanent = long-term, recoverable [OK]

Hint: Permanent tables keep data safe and recoverable long-term [OK]

Common Mistakes:

• Confusing transient with permanent tables
• Thinking temporary tables persist beyond session
• Assuming transient tables have fail-safe

2. Which of the following is the correct syntax to create a temporary table named session_data with columns id INT and value STRING in Snowflake?

easy

A. CREATE TABLE session_data TEMPORARY (id INT, value STRING);

B. CREATE TABLE TEMP session_data (id INT, value STRING);

C. CREATE TEMPORARY TABLE session_data (id INT, value STRING);

D. CREATE TEMP session_data (id INT, value STRING);

Solution

1. Step 1: Recall Snowflake syntax for temporary tables

   The correct keyword is TEMPORARY placed right after CREATE and before TABLE.

2. Step 2: Check each option's syntax

   CREATE TEMPORARY TABLE session_data (id INT, value STRING); uses correct order and keywords. Options A, B, and C use incorrect or unsupported syntax.

3. Final Answer:

   CREATE TEMPORARY TABLE session_data (id INT, value STRING); -> Option C

4. Quick Check:

   CREATE TEMPORARY TABLE = correct syntax [OK]

Hint: Use CREATE TEMPORARY TABLE for temporary tables [OK]

Common Mistakes:

• Using TEMP instead of TEMPORARY
• Placing TEMPORARY after table name
• Omitting TABLE keyword

3. What will be the result of the following Snowflake SQL commands?

CREATE TRANSIENT TABLE temp_cost (item STRING, price NUMBER);
INSERT INTO temp_cost VALUES ('apple', 1.2);
SELECT * FROM temp_cost;

medium

A. Syntax error due to TRANSIENT keyword

B. Error: Table does not exist

C. Empty result set

D. [{'item': 'apple', 'price': 1.2}]

Solution

1. Step 1: Understand transient table behavior

   Transient tables behave like permanent tables but without fail-safe. They accept inserts and can be queried normally.

2. Step 2: Analyze the commands

   The table is created, a row is inserted, and then selected. No errors or empty results expected.

3. Final Answer:

   [{'item': 'apple', 'price': 1.2}] -> Option D

4. Quick Check:

   Transient tables store and return inserted data [OK]

Hint: Transient tables act like permanent but no fail-safe [OK]

Common Mistakes:

• Thinking transient tables cannot store data
• Expecting syntax error with TRANSIENT keyword
• Assuming transient tables auto-delete data immediately

4. You run the following command in Snowflake:

CREATE TEMPORARY TABLE temp_users (user_id INT, name STRING);

Later, you try to query temp_users in a new session but get an error. What is the most likely cause?

medium

A. Temporary tables only exist during the session they were created in

B. Syntax error in table creation

C. Transient tables cannot be queried

D. Table was dropped manually

Solution

1. Step 1: Recall temporary table lifecycle

   Temporary tables exist only for the duration of the session that created them.

2. Step 2: Understand session behavior

   Querying in a new session fails because the temporary table no longer exists.

3. Final Answer:

   Temporary tables only exist during the session they were created in -> Option A

4. Quick Check:

   Temporary = session-only lifespan [OK]

Hint: Temp tables vanish after session ends [OK]

Common Mistakes:

• Assuming temp tables persist across sessions
• Confusing transient with temporary tables
• Ignoring session scope of temporary tables

5. You want to create a table in Snowflake that stores temporary data across sessions but does not use fail-safe to reduce storage costs. Which table type and creation statement should you use?

hard

A. CREATE TRANSIENT TABLE cost_savings (id INT, amount NUMBER);

B. CREATE TEMPORARY TABLE cost_savings (id INT, amount NUMBER);

C. CREATE PERMANENT TABLE cost_savings (id INT, amount NUMBER);

D. CREATE EXTERNAL TABLE cost_savings (id INT, amount NUMBER);

Solution

1. Step 1: Identify table types and fail-safe behavior

   Transient tables do not have fail-safe, reducing storage costs but keep data beyond session.

2. Step 2: Match requirement with table type

   Temporary tables are session-only, permanent tables have fail-safe, external tables are for external data.

3. Final Answer:

   CREATE TRANSIENT TABLE cost_savings (id INT, amount NUMBER); -> Option A

4. Quick Check:

   Transient = no fail-safe, cost-saving [OK]

Hint: Use transient tables to save costs without fail-safe [OK]

Common Mistakes:

• Choosing temporary tables which expire after session
• Using permanent tables with fail-safe enabled
• Confusing external tables with transient