Secure Data Sharing

Snowflake Management, Governance & Collaboration

Emily Melhuish

Technical Curriculum Developer, Snowflake

Problem with Traditional Data Sharing

How Snowflake Sharing Works

Diagram showing traditional data pipeline with extract, transfer, and load steps between two organizations

Creating The Share

CREATE SHARE claro_credit_risk_share; -- Step 1

GRANT USAGE ON DATABASE credit_risk_db -- Step 2
  TO SHARE claro_credit_risk_share;
GRANT USAGE ON SCHEMA credit_risk_db.analytics
  TO SHARE claro_credit_risk_share;
GRANT SELECT ON TABLE credit_risk_db.analytics.risk_summary
  TO SHARE claro_credit_risk_share;

ALTER SHARE claro_credit_risk_share -- Step 3
  ADD ACCOUNTS = partner_bank.eu_west;

Mounting a Share

-- Consumer creates a database from the share
CREATE DATABASE claro_shared_data
  FROM SHARE claro.eu_west.claro_credit_risk_share;

-- Query it like any other database
SELECT *
FROM claro_shared_data.analytics.risk_summary;

Reader Accounts

Not every partner has a Snowflake account
Claro creates a reader account on the partner's behalf
Partner queries the share with provided credentials
Trade-off: Claro pays for the reader's compute

Secure data sharing.png

Data sharing.png

Secure Views in Sharing

Default: SECURE_OBJECTS_ONLY = TRUE
While not recommended, you can set SECURE_OBJECTS_ONLY = FALSE

¹ https://docs.snowflake.com/en/user-guide/data-sharing-secure-views

Let's practice!

Snowflake Management, Governance & Collaboration