Skip to main content
Access to the Blockworks Snowflake Datashare is arranged with our team. Once the share is granted, mounting it in your account takes a few minutes and two SQL statements.

​
1. Request access

Contact Blockworks

Get in touch at blockworks.com/contact to discuss datashare access.
To speed things along, have the following ready:
Find your account identifier by running SELECT CURRENT_ORGANIZATION_NAME(), CURRENT_ACCOUNT_NAME(); in Snowflake, or by reading it from the account selector in Snowsight.
Snowflake Secure Data Sharing is direct only between accounts in the same cloud provider and region. If your account is in a different region, tell us up front. Cross-region delivery is arranged differently, and knowing early avoids a false start.

​
2. Find the share

Once we have granted the share to your account, it appears in your Snowflake account under Data Products, then Private Sharing, in Snowsight, listed as a share awaiting setup. To confirm it from SQL, use a role with the ACCOUNTADMIN role (or a role with the IMPORT SHARE privilege):
The Blockworks share appears as an inbound share. Note its fully qualified name, the <provider_account>.<share_name> value in the output. You will use it in the next step.

​
3. Create a database from the share

Mounting the share creates a read-only database in your account. Nothing is copied; the database is a live view onto the shared data.
BLOCKWORKS here is the local database name in your account, so pick whatever fits your naming conventions. <provider_account>.<share_name> is the value from SHOW SHARES.

​
4. Grant access to your roles

A database created from a share is read-only, and its privileges are granted as a unit with IMPORTED PRIVILEGES.
Repeat for each role that needs access. Grant to the narrowest set of roles that need the data.

​
5. Verify

If you see the shared schemas, you are connected. Head to Querying in Snowflake to explore what is in them.

​
Troubleshooting

Confirm you are running as ACCOUNTADMIN, and that the account identifier you gave us matches the account you are checking, since organizations often have several. If it still does not appear, come back to us with the exact identifier you ran SHOW SHARES in.
This usually means the executing role lacks the IMPORT SHARE privilege, or the share name is not fully qualified. It must include the provider account prefix, exactly as SHOW SHARES reports it.
Their role needs IMPORTED PRIVILEGES on the shared database. Ordinary object-level grants do not apply to shared databases.
Direct shares do not cross cloud regions. Contact us so we can arrange delivery for your region.
These are the standard Snowflake consumer steps for a direct share. If your organization has its own conventions for mounting shares (a dedicated provisioning role, a naming standard, an infrastructure-as-code workflow), follow those. The only Blockworks-specific inputs are the share name and the account identifier you give us.