Sharing for Snowflakes
Sharing in Snowflake lets one account give another read access to live data without copying it. A provider creates a share containing selected objects, and consumers mount it as a read-only database. Reader accounts serve people without Snowflake, and the Marketplace lists datasets and apps from third parties for discovery and use.
Stage: Performance and Governance · Part of the Snowflake roadmap · Last reviewed 19 November 2026
What to learn in Sharing
- Create a share and add a database, schema and table to it
- Mount a share as a database in a consumer account
- Explain why shared data is not copied and stays current
- Create a reader account for a partner without their own account
- Evaluate and obtain a listing from the Snowflake Marketplace
Sharing interview questions
Does data sharing in Snowflake copy the data?
No. The consumer reads the provider's data in place through metadata pointers, so there is no transfer or duplicate storage, and changes appear immediately. The consumer pays for the compute they use to query it.
What is a reader account?
A reader account is a Snowflake account created and paid for by a provider for a consumer who does not have their own account. The consumer can query shared data but the provider manages the account and its compute cost.
Where Sharing fits in the Snowflake roadmap
Sharing belongs to the Performance and Governance stage (advanced level). Run it well.
Other units in this stage
Back to the full Snowflake roadmap