Share security and governance in Snowflake - Time & Space Complexity

Time Complexity: Share security and governance

O(n)

Understanding Time Complexity

We want to understand how the time to check and enforce share security and governance grows as more shares and users are involved.

How does Snowflake handle security checks when many shares and permissions exist?

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

-- List all shares accessible by a user
SHOW SHARES;

-- Check privileges on a specific share
SHOW GRANTS ON SHARE my_share;

-- Grant usage on a share to a role
GRANT USAGE ON SHARE my_share TO ROLE my_role;

-- Revoke usage on a share from a role
REVOKE USAGE ON SHARE my_share FROM ROLE my_role;

-- Describe share details
DESCRIBE SHARE my_share;
    

This sequence shows common commands to manage and check share security and governance in Snowflake.

Identify Repeating Operations

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

• Primary operation: Checking and updating share privileges and metadata.
• How many times: Each command runs once per user or admin action, but internally Snowflake checks permissions for each share and role involved.

How Execution Grows With Input

As the number of shares and roles grows, the system must check more permissions and metadata.

Input Size (n)	Approx. API Calls/Operations
10 shares/roles	About 10 permission checks
100 shares/roles	About 100 permission checks
1000 shares/roles	About 1000 permission checks

Pattern observation: The number of permission checks grows roughly in direct proportion to the number of shares and roles involved.

Final Time Complexity

Time Complexity: O(n)

This means the time to check and enforce share security grows linearly with the number of shares and roles.

Common Mistake

[X] Wrong: "Checking share permissions happens instantly no matter how many shares exist."

[OK] Correct: Each share and role adds more permission checks, so time grows with the number of shares and roles.

Interview Connect

Understanding how security checks scale helps you design systems that stay fast and safe as they grow.

Self-Check

"What if Snowflake cached share permissions for roles? How would the time complexity change?"

Practice

1. What is the main purpose of a share in Snowflake?

easy

A. To safely share data without copying or moving it

B. To create a backup of data in another region

C. To encrypt data before storage

D. To delete data from multiple accounts

Solution

1. Step 1: Understand the concept of a share

   A share in Snowflake allows data to be accessed by other accounts without physically moving or copying the data.

2. Step 2: Compare options with the concept

   The options describing encryption before storage, creating backups in another region, and deleting data from multiple accounts are unrelated to sharing data safely.

3. Final Answer:

   To safely share data without copying or moving it -> Option A

4. Quick Check:

   Share = Safe data access without moving [OK]

Hint: Shares let others see data without moving it [OK]

Common Mistakes:

• Thinking shares copy data to other accounts
• Confusing shares with backups
• Assuming shares encrypt data automatically

2. Which SQL command correctly grants usage on a share to a specific account in Snowflake?

easy

A. GRANT USAGE TO SHARE my_share ACCOUNT 'account_name';

B. GRANT SHARE ON USAGE my_share TO ACCOUNT 'account_name';

C. GRANT USAGE ON SHARE my_share TO ACCOUNT = 'account_name';

D. GRANT ACCOUNT USAGE ON SHARE my_share TO 'account_name';

Solution

1. Step 1: Recall correct GRANT syntax for shares

   The correct syntax is: GRANT USAGE ON SHARE <share_name> TO ACCOUNT = '<account_name>';

2. Step 2: Check each option's syntax

   Only GRANT USAGE ON SHARE my_share TO ACCOUNT = 'account_name'; matches the correct syntax. Others have incorrect order or missing keywords.

3. Final Answer:

   GRANT USAGE ON SHARE my_share TO ACCOUNT = 'account_name'; -> Option C

4. Quick Check:

   GRANT USAGE ON SHARE ... TO ACCOUNT = ... [OK]

Hint: GRANT USAGE ON SHARE ... TO ACCOUNT = 'name' [OK]

Common Mistakes:

• Swapping keywords order
• Omitting the equal sign after ACCOUNT
• Using incorrect object types in GRANT

3. Given the following SQL commands, what will be the result when account 'A' tries to query the shared table?

CREATE SHARE my_share;
GRANT USAGE ON DATABASE my_db TO SHARE my_share;
GRANT SELECT ON TABLE my_db.public.my_table TO SHARE my_share;
GRANT USAGE ON SHARE my_share TO ACCOUNT = 'A';

medium

A. Account 'A' cannot query because database usage is not granted

B. Account 'A' can query my_table successfully

C. Account 'A' cannot query because SELECT privilege is missing

D. Account 'A' cannot query because share usage is not granted

Solution

1. Step 1: Check granted privileges on share

   The share has USAGE on the database and SELECT on the table granted, and account 'A' has USAGE on the share.

2. Step 2: Confirm account 'A' can access shared data

   With these grants, account 'A' can query the shared table successfully.

3. Final Answer:

   Account 'A' can query my_table successfully -> Option B

4. Quick Check:

   Proper grants = Access allowed [OK]

Hint: Grant database usage, table select, and share usage to account [OK]

Common Mistakes:

• Forgetting to grant USAGE on database to share
• Missing SELECT privilege on table
• Not granting USAGE on share to account

4. You receive an error when trying to grant SELECT on a table to a share: SQL compilation error: Insufficient privileges. What is the most likely cause?

medium

A. You forgot to create the database

B. The share does not exist

C. The account name is misspelled

D. You do not have OWNERSHIP privilege on the table

Solution

1. Step 1: Understand privilege requirements for granting SELECT to share

   Granting SELECT on a table to a share requires OWNERSHIP or appropriate privileges on that table.

2. Step 2: Analyze error cause

   Insufficient privileges error usually means the user lacks OWNERSHIP or necessary rights on the table.

3. Final Answer:

   You do not have OWNERSHIP privilege on the table -> Option D

4. Quick Check:

   OWNERSHIP needed to grant SELECT to share [OK]

Hint: OWNERSHIP needed to grant privileges on objects [OK]

Common Mistakes:

• Assuming share existence causes privilege errors
• Confusing account name typos with privilege errors
• Ignoring ownership requirements

5. You want to share a subset of data securely with multiple external accounts but restrict access to only certain tables and columns. Which Snowflake feature combination should you use?

hard

A. Create a share with specific tables and use secure views to limit columns, then grant share usage to accounts

B. Create a share with all tables and rely on account-level access control

C. Copy data to each account and grant full access

D. Use database replication to share data and restrict columns via masking policies

Solution

1. Step 1: Identify how to limit tables and columns in shares

   Shares can include specific tables only. To restrict columns, secure views can be created exposing only allowed columns.

2. Step 2: Confirm how to share with multiple accounts securely

   Granting USAGE on the share to multiple accounts allows controlled access without copying data.

3. Final Answer:

   Create a share with specific tables and use secure views to limit columns, then grant share usage to accounts -> Option A

4. Quick Check:

   Shares + secure views = controlled multi-account access [OK]

Hint: Use secure views inside shares to limit columns [OK]

Common Mistakes:

• Sharing all tables without column restrictions
• Copying data instead of sharing
• Using replication which is for disaster recovery, not sharing