Reader accounts for non-Snowflake users - Time & Space Complexity

Time Complexity: Reader accounts for non-Snowflake users

O(n)

Understanding Time Complexity

We want to understand how the work grows when using reader accounts for users outside Snowflake.

Specifically, how does the number of operations change as more external users access data?

Scenario Under Consideration

Analyze the time complexity of this sequence creating and using reader accounts.

CREATE READER ACCOUNT reader_acc;
GRANT USAGE ON DATABASE sales_db TO READER ACCOUNT reader_acc;
-- External user connects using reader_acc
SELECT * FROM sales_db.public.orders;
-- Repeat for multiple external users

This sequence sets up a reader account and external users query data through it.

Identify Repeating Operations

Look at what happens repeatedly when many external users access data.

• Primary operation: External queries through the reader account.
• How many times: Once per external user query.

How Execution Grows With Input

As more external users query data, the number of queries grows directly with users.

Input Size (n)	Approx. API Calls/Operations
10	10 queries through reader account
100	100 queries through reader account
1000	1000 queries through reader account

Pattern observation: The work grows in a straight line as users increase.

Final Time Complexity

Time Complexity: O(n)

This means the number of operations grows directly with the number of external users querying data.

Common Mistake

[X] Wrong: "Adding more external users does not increase query operations because they share the same reader account."

[OK] Correct: Each external user runs their own queries, so the total queries increase with users, even if the reader account is shared.

Interview Connect

Understanding how external user queries scale helps you design data sharing solutions that handle growth smoothly.

Self-Check

"What if each external user had their own reader account instead of sharing one? How would the time complexity change?"

Practice

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

easy

A. To monitor Snowflake account usage and billing

B. To allow non-Snowflake users to access shared data securely

C. To manage user permissions within a Snowflake account

D. To create a backup of Snowflake data

Solution

1. Step 1: Understand the role of Reader Accounts

   Reader accounts are designed to let users without Snowflake accounts access shared data safely.

2. Step 2: Compare options with this purpose

   The options for monitoring usage, creating backups, and managing user permissions describe other Snowflake features unrelated to Reader Accounts.

3. Final Answer:

   To allow non-Snowflake users to access shared data securely -> Option B

4. Quick Check:

   Reader Account purpose = secure data access for non-users [OK]

Hint: Reader accounts = access for users without Snowflake [OK]

Common Mistakes:

• Confusing Reader accounts with user management
• Thinking Reader accounts are for backups
• Assuming Reader accounts monitor billing

2. Which SQL command is used to create a Reader Account from an existing share in Snowflake?

easy

A. CREATE READER ACCOUNT

B. CREATE ACCOUNT READER

C. CREATE READER ACCOUNT FROM SHARE

D. CREATE SHARE READER ACCOUNT

Solution

1. Step 1: Recall the correct syntax for creating Reader Accounts

   The correct command is CREATE READER ACCOUNT ... FROM SHARE ... followed by parameters.

2. Step 2: Eliminate incorrect syntax options

   Only CREATE READER ACCOUNT FROM SHARE matches the correct syntax including the FROM SHARE clause.

3. Final Answer:

   CREATE READER ACCOUNT FROM SHARE -> Option C

4. Quick Check:

   Command to create Reader Account from share = CREATE READER ACCOUNT FROM SHARE [OK]

Hint: Remember exact phrase: CREATE READER ACCOUNT FROM SHARE [OK]

Common Mistakes:

• Omitting FROM SHARE clause
• Swapping word order
• Combining CREATE and SHARE incorrectly

3. Given the SQL snippet:

CREATE READER ACCOUNT partner_reader FROM SHARE partner_share;

What is the expected result of this command?

medium

A. Grants partner_share access to the partner_reader account

B. Creates a new share named partner_reader from the account partner_share

C. Deletes the share named partner_share

D. Creates a new Snowflake account named partner_reader with access to partner_share data

Solution

1. Step 1: Analyze the CREATE READER ACCOUNT command

   This command creates a new reader account named partner_reader that can access data shared via partner_share.

2. Step 2: Understand the relationship between reader account and share

   The reader account is a new Snowflake account for external users, linked to the existing share.

3. Final Answer:

   Creates a new Snowflake account named partner_reader with access to partner_share data -> Option D

4. Quick Check:

   CREATE READER ACCOUNT creates account with share access [OK]

Hint: Reader account = new account accessing existing share [OK]

Common Mistakes:

• Confusing share creation with reader account creation
• Thinking the share is deleted
• Mixing up grant and create commands

4. You run this command:

CREATE READER ACCOUNT my_reader FROM SHARE;

But get an error. What is the likely cause?

medium

A. Missing share name after FROM SHARE

B. Reader accounts cannot be created from shares

C. Syntax requires USING keyword before share name

D. Reader account name cannot contain underscores

Solution

1. Step 1: Check the command syntax

   The command must specify the share name after FROM SHARE. Here, it is missing.

2. Step 2: Verify other options

   Reader accounts can be created from shares, no USING keyword is needed, and underscores are allowed in names.

3. Final Answer:

   Missing share name after FROM SHARE -> Option A

4. Quick Check:

   FROM SHARE must be followed by share name [OK]

Hint: Always specify share name after FROM SHARE [OK]

Common Mistakes:

• Omitting share name
• Adding unnecessary keywords
• Assuming naming restrictions that don't exist

5. A company wants to share data with a partner who does not have a Snowflake account. Which steps correctly describe how to enable this using Reader Accounts?

hard

A. Create a share with the data, then create a Reader Account from that share for the partner

B. Create a Reader Account first, then create a share inside that account

C. Ask the partner to create a Snowflake account, then grant access

D. Export data to CSV and send it manually

Solution

1. Step 1: Understand Reader Account workflow

   First, create a share containing the data to share.

2. Step 2: Create a Reader Account from the share

   This creates a Snowflake account for the partner to access the shared data without needing their own account.

3. Step 3: Evaluate other options

   Create a Reader Account first, then create a share inside that account reverses the order incorrectly; C requires partner to have an account; D is manual and not using Snowflake features.

4. Final Answer:

   Create a share with the data, then create a Reader Account from that share for the partner -> Option A

5. Quick Check:

   Share data first, then create Reader Account [OK]

Hint: Share data first, then create Reader Account [OK]

Common Mistakes:

• Creating Reader Account before share
• Assuming partner must have Snowflake account
• Using manual data export instead of Reader Account