Knowledge Base

Intro

Gryd by BuildZoom Data Snowflake Share delivers your subscribed datasets as live secure views inside your own Snowflake account. No file transfers, no copies, always up to date with your subscription's refresh cadence.

Features

Secure Views for each dataset

• Gryd by BuildZoom Data will create secure views against 1 or more output tables subscribed to by the customer.
• Each Secure View is in turn granted to a new Snowflake Share connected to the customer's Snowflake Account.
• Whenever this data subscription is run (monthly/weekly etc.) the data is reflected in these output tables and immediately available to the secure views.

Data Refresh Status - An additional secure view with summary statistics

Requirements/Limitations

• Snowflake direct share is only currently supported between Snowflake accounts within the same Cloud Provider and Region.
• This is currently AWS_US_EAST_1 (display name: US East (N. Virginia) )
• Customers can use SELECT CURRENT_REGION(); to confirm their region and provider.

Set-Up

• The customer will need to provide Gryd with the OrganizationID and AccountID of the customer's Snowflake account.
• This can be found by navigating to a user's Profile in the bottom left of Snowsight, expanding the list of active accounts, and selecting "view account details" for the desired account.
• From the returned table, find the "Data sharing account identifier", which is in the format OrganizationID.AccountID; separated by a period.

Client Instructions: confirm successful share

Step 1: Confirm the Gryd share is visible to your account.

SHOW SHARES;
-- Look for kind = INBOUND with name ending in .BUILDZOOMDATA__SHARE
-- Note the fully-qualified name in the "name" column: ..BUILDZOOMDATA__SHARE

Step 2: Create a local database from the share. Replace <BZD_ORG>.<BZD_ACCOUNT> with the fully-qualified name from Step 1.

CREATE DATABASE IF NOT EXISTS  e.g. "shared_from_buildzoomdata"
FROM SHARE ..BUILDZOOMDATA__SHARE;

Optionally grant access to other roles in your account:

GRANT IMPORTED PRIVILEGES ON DATABASE  TO ROLE ;

Step 3: Confirm the shared views are present. The share exposes secure views (not tables) in the your schema.

SHOW VIEWS IN SCHEMA .;
-- expect: _properties, _building_permits,
-- _building_permit_classifications,
-- _building_permit_statuses, _permit_jurisdiction_stats

Step 4: Query the data. Select directly from the live views, or use ELT to copy/upsert into your own persistent tables.

-- Spot-check the data:
SELECT * FROM .._properties LIMIT 100;
SELECT * FROM .._building_permits LIMIT 100;

-- Check data freshness / coverage:
SELECT * FROM .._permit_jurisdiction_stats;