Course contents

SnowPro Core COF-C03 Study GuidePart 5: Data protection and sharingReader Accounts

Reader Accounts

Reader Accounts

Definition

A reader account is a Snowflake account the provider creates and owns, on behalf of a consumer who has no Snowflake account of their own. It can only read data shared by the provider that created it, can't load or change data, and the provider pays its compute.

The IsmaFrost version: a retail partner with no Snowflake account needs weekly sell-through data. Youness creates a reader account, adds it as a consumer on the share, creates one small warehouse and one login inside it, and hands the partner a URL. The partner queries live data in a browser; every credit their queries burn lands on IsmaFrost's bill, which is also why the warehouse Youness gave them is an X-Small with AUTO_SUSPEND = 60 and a resource monitor of its own. One reader account per partner, never a shared one, so revoking a relationship is one drop, not a password rotation for everyone.

Reader account. The provider IsmaFrost runs CREATE MANAGED ACCOUNT with TYPE = READER and adds the new account to SALES_SHARE. Inside the reader account, SHARED_SALES is a read-only database from the share and READER_WH is a warehouse the provider creates. A retail partner without a Snowflake account signs in with the URL and login the provider hands over. Every credit READER_WH uses is billed to IsmaFrost.PROVIDER · ISMAFROSTREADER ACCOUNTSHARESALES_SHAREthe existing shareSTATEMENTCREATE MANAGEDACCOUNT … READERCOSTPays reader creditson the IsmaFrost billDATABASE FROM SHARESHARED_SALESread-only, from shareWAREHOUSEREADER_WHcreated by providerCONSUMERPartnerno Snowflakeaccountcreated, owned and paid by IsmaFrostRead-only: no loading, no DML. One reader account per external organization.grantedcreatesbilledsigns inqueries

PROVIDER · ISMAFROST

READER ACCOUNT

SHARESALES_SHAREthe existing share

granted

DATABASE FROM SHARESHARED_SALESread-only, from share

STATEMENTCREATE MANAGED ACCOUNT … READER

creates

queries

COSTPays reader creditson the IsmaFrost bill

billed

WAREHOUSEREADER_WHcreated by provider

created, owned and paid by IsmaFrost

signs in

CONSUMERPartnerno Snowflake account

Read-only: no loading, no DML. One reader account per external organization.

Figure 5.6 A reader account lets someone without Snowflake query your share, and you pay for it. The provider creates the account, adds it to the share and sets up its warehouse; the partner only signs in, and every credit lands on the provider's bill.

A sound design for an unknown mix of Snowflake and non-Snowflake consumers: give each non-Snowflake consumer its own reader account rather than pooling unrelated parties in one, because a shared reader account mixes their billing, isolation and access. A reader account lives in the provider's region. For a consumer in another region or cloud, replicate the database and the share to an account you own in that region and share from there, or publish a listing with Cross-Cloud Auto-Fulfillment.

Exam trap

Reader accounts are billed to the provider, not the reader. A scenario proposing that the consumer pays their own reader-account compute is always wrong; that defeats the entire "no Snowflake account needed" pitch to a non-Snowflake customer.