Secure Data Sharing & the Marketplace
Snowflake's most distinctive feature: sharing live data with other accounts in the same region without copying it, and without the recipient needing to be a Snowflake customer at all (through a reader account, next section).
Secure Data Sharing Fundamentals
A share is a named account-level object granting read-only access to specific databases, schemas, tables, or secure views, to one or more consumer accounts, without copying the underlying micro-partitions. The consumer queries live data directly against the provider's storage. A direct share works only with consumers in the provider's region (listings, two sections on, cross regions).
ONE CLOUD REGION · DIRECT SHARES STAY INSIDE IT
PROVIDER ACCOUNT · ISMAFROST
CONSUMER ACCOUNT · PARTNER
SHARESALES_
ACCOUNTS
DATABASE FROM SHARESHARED_
GRANT … TO SHARE
reads live data
runs the queries
DATABASESALES_DBthe data lives here
WAREHOUSEPARTNER_
Pays: storage
Pays: compute
-- Provider sideCREATE SHARE sales_share;GRANT USAGE ON DATABASE sales_db TO SHARE sales_share;GRANT USAGE ON SCHEMA sales_db. public TO SHARE sales_share; GRANT SELECT ON TABLE sales_db. public. orders TO SHARE sales_share; ALTER SHARE sales_share ADD ACCOUNTS = consumer_org. consumer_ acct; -- Consumer side: mount the share as a read-only databaseCREATE DATABASE shared_sales FROM SHARE provider_org. provider_ acct. sales_ share;
To let other roles on the consumer side query the shared database, run GRANT IMPORTED PRIVILEGES ON DATABASE shared_sales TO ROLE analyst. It joins with local tables like any other database.
| In a direct share | Provider (IsmaFrost) | Consumer (partner) |
|---|---|---|
| Storage | Keeps the data and pays for its storage | Stores nothing: the database created from the share is 0 bytes |
| Compute | Pays nothing for the consumer's queries | Queries with its own warehouse and pays that compute |
| What is shared, with whom | GRANT … TO SHARE, then ALTER SHARE … ADD ACCOUNTS | CREATE DATABASE … FROM SHARE |
| Changing the data | Any change is visible to the consumer immediately | Read-only: no DML, no clone, no Time Travel; re-sharing only to accounts in its own organization, when the provider allows it |
| Views in the share | Secure views by default; plain views only in a share created with SECURE_ | Can't read a secure view's definition |
Only secure views (a plain view fits only in a share that allows non-secure objects, and it can leak filtered rows) should sit between raw data and a share when filtering is involved, since a secure view hides its definition and disables optimizer shortcuts that could otherwise leak filtered-out rows to a sufficiently clever consumer query. Masking and row access policies on shared tables are enforced for the consumer too, but a secure view is the usual way to filter rows for a share.

