Data Sharing and Snowflake Marketplace · Topic 5 of 10

Reader Accounts - Create, Users, Resource Monitors and Objects

Create and maintain Snowflake reader accounts, set up users and roles, add resource monitors, see what can be created, and decide if data needs storing.

  • 5 min
In a nutshell
  • CREATE MANAGED ACCOUNT ... TYPE = READER; the provider pays all compute.
  • Same edition and region as the provider; 75 accounts by default.
  • The reader administrator creates users, roles, the shared database and resource monitors.

What it is

A reader account is a Snowflake account that a provider creates and manages for a consumer who does not have a Snowflake account of their own. The consumer can query the provider's shared data without signing a Snowflake contract.

The provider owns the reader account in every way that matters: it has the same edition and region as the provider, and the provider pays for all credits the reader account consumes. That makes cost control the main administrative job.

Provider accountowns data and paysCREATE MANAGED ACCOUNTReader accountsame edition and regionshare addedShared databaseread onlyqueried byConsumer usersreader users

How it works

Create and maintain reader accounts

The provider uses ACCOUNTADMIN, or a role with the CREATE ACCOUNT privilege.

CREATE MANAGED ACCOUNT partner_reader
  ADMIN_NAME = reader_admin,
  ADMIN_PASSWORD = '<set a strong password>',
  TYPE = READER;

In Snowsight the same step is under Admin, Accounts, Reader accounts, then New. The result gives the account name, the account locator and the login URL. Wait a few minutes for the account to be provisioned.

Then the provider adds the reader account to a share, using the locator.

ALTER SHARE sales_share ADD ACCOUNTS = <reader_account_locator>;
TaskCommand or fact
List reader accountsSHOW MANAGED ACCOUNTS
Remove a reader accountDROP MANAGED ACCOUNT
Limit75 reader accounts per provider by default; Snowflake Support can raise it
After a dropThe account still counts toward the limit for 7 days
Edition and regionSame as the provider
Who paysThe provider, for all credits used

Reader accounts cannot be used as clean room participants and cannot be marketplace providers.

Exam tip

A reader account solves "partner has no Snowflake account". If the partner could simply get an account, a direct share or listing to their own account is better, because they then pay their own compute.

Create a user and a role for access

The reader account starts with one administrator, the user named in ADMIN_NAME, who holds ACCOUNTADMIN in that account. The provider gives these credentials to the consumer, who signs in at the login URL.

The administrator then builds access exactly as in any account.

USE ROLE ACCOUNTADMIN;
CREATE ROLE reader_analyst;
CREATE USER ann PASSWORD = '<temporary password>' MUST_CHANGE_PASSWORD = TRUE
  DEFAULT_ROLE = reader_analyst;
GRANT ROLE reader_analyst TO USER ann;
CREATE DATABASE partner_sales FROM SHARE myorg.provider_acct.sales_share;
GRANT IMPORTED PRIVILEGES ON DATABASE partner_sales TO ROLE reader_analyst;

Key points:

  • The user needs a role that holds IMPORTED PRIVILEGES on the shared database and USAGE on a warehouse.
  • The shared database is created once from the share, by the reader administrator.
  • Use roles rather than granting access to users, and keep the reader administrator for administration only.

Create resource monitors

A reader account has no credit limit by default. Its warehouses can use an unlimited number of credits each month, and the provider is billed. Snowflake recommends a resource monitor on every warehouse.

USE ROLE ACCOUNTADMIN;
CREATE RESOURCE MONITOR reader_cap WITH CREDIT_QUOTA = 20
  FREQUENCY = MONTHLY START_TIMESTAMP = IMMEDIATELY
  TRIGGERS ON 80 PERCENT DO NOTIFY
           ON 100 PERCENT DO SUSPEND;
ALTER WAREHOUSE reader_wh SET RESOURCE_MONITOR = reader_cap;
TriggerEffect
NOTIFYSends a notice at the threshold
SUSPENDSuspends assigned warehouses after running queries finish
SUSPEND_IMMEDIATESuspends right away and cancels running queries

Set the quota with the consumer, and set AUTO_SUSPEND low on the warehouse so that it does not burn credits while idle.

Reader warehouseruns queriesusage counted byResource monitorcredit quotaat 80 percentNotifyadminResource monitorat 100 percentSuspendwarehouse stops

Create objects and decide if data must be stored

Reader accounts are built for reading. What users can do:

  • Query shared data, and create objects that work on it, such as views and materialized views.
  • Create users, roles, warehouses and resource monitors, because the reader administrator needs them to operate.
  • Create the database from the share.

What users cannot do:

  • Load or change data: INSERT, UPDATE, DELETE, MERGE and COPY INTO <table> are not allowed.
  • Create shares, stages, pipes or services, or create masking and row access policies.
  • Refresh dynamic tables.

So the question "is there a need to store data in the reader account" has a clear answer. If the consumer only reads shared data, nothing is stored, and the only database is the one created from the share. If the consumer needs to load its own data, a reader account is the wrong tool; that consumer needs a full Snowflake account.

Consumer needFit
Read provider data with their own usersReader account
Join provider data with their own filesFull account, not reader
Load and transform dataFull account
No Snowflake account, limited budget controlReader account with resource monitors

Common mistakes

No resource monitor. The provider receives the bill for runaway queries.

Handing out the administrator login to everyone. Create users and roles instead.

Using a reader account to load data. DML and loading are blocked.

Expecting an unlimited number of reader accounts. The default is 75.

Forgetting IMPORTED PRIVILEGES. The user sees an empty list of databases.

What to remember for the exam

  • CREATE MANAGED ACCOUNT ... TYPE = READER; the provider pays all compute.
  • Same edition and region as the provider; 75 accounts by default.
  • The reader administrator creates users, roles, the shared database and resource monitors.
  • Reader accounts are read only for shared data; no loading and no DML.
  • Always add a resource monitor to reader warehouses.

Check yourself

  • Who pays for queries run in a reader account?

    The provider account that created it.

  • Can reader account users load their own files?

    No. COPY INTO <table> and DML are not allowed, so such users need a full account.

  • How is a reader account's spending limited?

    With a resource monitor with a credit quota, assigned to its warehouses.

Topic 5 of 10 in Data Sharing and Snowflake Marketplace

Test yourself on Data Sharing and Snowflake Marketplace

The full Snowflake ADA-C02 question bank has 814 questions, with timed practice exams and an explanation for every answer.

This study guide is independent and is not affiliated with, endorsed by, or sponsored by Snowflake. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.