Creating custom roles in Snowflake - Performance & Efficiency

Time Complexity: Creating custom roles

O(n)

Understanding Time Complexity

When creating custom roles in Snowflake, it's important to understand how the time to create roles grows as you add more roles.

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

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

-- Create multiple custom roles
BEGIN
  FOR i IN 1..n LOOP
    EXECUTE IMMEDIATE 'CREATE ROLE role_' || i;
  END LOOP;
END;
    

This sequence creates n custom roles one by one using a loop.

Identify Repeating Operations

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

• Primary operation: Executing the 'CREATE ROLE' command for each role.
• How many times: Exactly n times, once per role.

How Execution Grows With Input

Each new role requires one separate create command, so the total operations increase directly with the number of roles.

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

Pattern observation: The number of operations grows linearly as you add more roles.

Final Time Complexity

Time Complexity: O(n)

This means the time to create roles grows directly in proportion to how many roles you create.

Common Mistake

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

[OK] Correct: Each role creation is a separate command that takes time, so more roles mean more commands and more time.

Interview Connect

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

Self-Check

"What if we created roles in parallel instead of one by one? How would the time complexity change?"

Practice

1. What is the main purpose of creating a custom role in Snowflake?

easy

A. To create a new user account

B. To store data in a new database

C. To run SQL queries faster

D. To control and manage user access permissions

Solution

1. Step 1: Understand role purpose

   Custom roles in Snowflake are designed to manage what users can do by controlling permissions.

2. Step 2: Identify correct function

   Creating a role is not about storing data, creating users, or speeding queries, but about access control.

3. Final Answer:

   To control and manage user access permissions -> Option D

4. Quick Check:

   Role purpose = Access control [OK]

Hint: Roles control permissions, not data or users [OK]

Common Mistakes:

• Confusing roles with users
• Thinking roles store data
• Assuming roles speed up queries

2. Which of the following is the correct syntax to create a new role named data_analyst in Snowflake?

easy

A. CREATE ROLE data_analyst;

B. NEW ROLE data_analyst;

C. MAKE ROLE data_analyst;

D. ADD ROLE data_analyst;

Solution

1. Step 1: Recall Snowflake role creation syntax

   The correct command to create a role is CREATE ROLE role_name;.

2. Step 2: Match syntax with options

   Only CREATE ROLE data_analyst; uses the correct CREATE ROLE syntax.

3. Final Answer:

   CREATE ROLE data_analyst; -> Option A

4. Quick Check:

   CREATE ROLE = correct syntax [OK]

Hint: Use CREATE ROLE to make new roles [OK]

Common Mistakes:

• Using NEW ROLE instead of CREATE ROLE
• Using MAKE or ADD which are invalid
• Missing semicolon at the end

3. Given the commands:

CREATE ROLE analyst;
GRANT USAGE ON DATABASE sales_db TO ROLE analyst;
GRANT ROLE analyst TO USER alice;

What permission does user alice have on sales_db?

medium

A. No permissions on sales_db

B. Only USAGE permission on sales_db

C. ALL permissions on sales_db

D. SELECT permission on sales_db

Solution

1. Step 1: Analyze role creation and grants

   The role analyst is created and given USAGE permission on sales_db.

2. Step 2: Check role assignment to user

   User alice is granted the analyst role, so she inherits its permissions.

3. Final Answer:

   Only USAGE permission on sales_db -> Option B

4. Quick Check:

   Role grants USAGE, user inherits USAGE [OK]

Hint: User gets permissions of assigned roles [OK]

Common Mistakes:

• Assuming no permissions without direct grant
• Confusing USAGE with SELECT permission
• Ignoring role inheritance

4. You run this command:

CREATE ROLE analyst

but get an error. What is the likely cause?

medium

A. You must create a user before creating a role

B. Role name analyst is reserved and cannot be used

C. Missing semicolon at the end of the command

D. CREATE ROLE command is not supported in Snowflake

Solution

1. Step 1: Check command syntax

   Snowflake commands require a semicolon at the end to execute properly.

2. Step 2: Evaluate other options

   Role names like analyst are allowed, users are independent of roles, and CREATE ROLE is supported.

3. Final Answer:

   Missing semicolon at the end of the command -> Option C

4. Quick Check:

   Semicolon ends command [OK]

Hint: Always end SQL commands with a semicolon [OK]

Common Mistakes:

• Forgetting semicolon causes syntax error
• Thinking role names are restricted
• Believing users must exist first

5. You want to create a custom role report_viewer that can only read data from the reports schema in the analytics database. Which sequence of commands correctly achieves this?

hard

A. CREATE ROLE report_viewer;
GRANT USAGE ON DATABASE analytics TO ROLE report_viewer;
GRANT USAGE ON SCHEMA analytics.reports TO ROLE report_viewer;
GRANT SELECT ON ALL TABLES IN SCHEMA analytics.reports TO ROLE report_viewer;

B. CREATE ROLE report_viewer;
GRANT SELECT ON DATABASE analytics TO ROLE report_viewer;

C. CREATE ROLE report_viewer;
GRANT ALL ON SCHEMA analytics.reports TO ROLE report_viewer;

D. CREATE ROLE report_viewer;
GRANT USAGE ON DATABASE analytics TO ROLE report_viewer;
GRANT SELECT ON SCHEMA analytics.reports TO ROLE report_viewer;

Solution

1. Step 1: Create the role

   Use CREATE ROLE report_viewer; to make the role.

2. Step 2: Grant USAGE on database and schema

   Granting USAGE on the database and schema allows access to objects inside.

3. Step 3: Grant SELECT on all tables in the schema

   Grant SELECT on all tables to allow read access to data.

4. Step 4: Evaluate options

   CREATE ROLE report_viewer; GRANT USAGE ON DATABASE analytics TO ROLE report_viewer; GRANT USAGE ON SCHEMA analytics.reports TO ROLE report_viewer; GRANT SELECT ON ALL TABLES IN SCHEMA analytics.reports TO ROLE report_viewer; correctly grants USAGE and SELECT at proper levels. CREATE ROLE report_viewer; GRANT SELECT ON DATABASE analytics TO ROLE report_viewer; misses schema and USAGE grants. CREATE ROLE report_viewer; GRANT ALL ON SCHEMA analytics.reports TO ROLE report_viewer; grants ALL which is too broad. CREATE ROLE report_viewer; GRANT USAGE ON DATABASE analytics TO ROLE report_viewer; GRANT SELECT ON SCHEMA analytics.reports TO ROLE report_viewer; grants SELECT on schema which is invalid; SELECT must be on tables.

5. Final Answer:

   CREATE ROLE report_viewer; GRANT USAGE ON DATABASE analytics TO ROLE report_viewer; GRANT USAGE ON SCHEMA analytics.reports TO ROLE report_viewer; GRANT SELECT ON ALL TABLES IN SCHEMA analytics.reports TO ROLE report_viewer; -> Option A

6. Quick Check:

   Grant USAGE + SELECT on tables = read access [OK]

Hint: Grant USAGE on DB/schema, SELECT on tables for read-only role [OK]

Common Mistakes:

• Granting SELECT on schema instead of tables
• Missing USAGE grants on database or schema
• Granting ALL permissions instead of SELECT only