> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blockdb.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Snowflake Share

> Access BlockDB blockchain datasets natively in Snowflake via Secure Data Sharing — no ETL required, CDC streams available.

## BlockDB on Snowflake Marketplace

Browse and request access to BlockDB datasets directly from the Snowflake Marketplace:

<Card title="BlockDB on Snowflake Marketplace" icon="snowflake" href="https://app.snowflake.com/marketplace/providers/GZ1MFZQTCWF/BlockDB">
  View all available BlockDB datasets, request a trial, and subscribe — no file handling or ETL required.
</Card>

## Why Use Snowflake Share

* Avoid managing raw files—datasets appear as ready-to-query tables inside your Snowflake account.
* Gain access to change streams for incremental processing without building your own CDC logic.
* Keep data in sync automatically; BlockDB operates the provider account and updates propagate in minutes.

## Provisioning Flow

1. Provide your Snowflake account locator (e.g., `xy12345.us-east-1`) to [support@blockdb.io](mailto:support@blockdb.io).
2. BlockDB creates a share containing the dataset schemas (`0101_blocks_v1`, `0102_transactions_v1`, etc.) and grants it to your account.
3. You create a database from the share:

```sql theme={null}
CREATE DATABASE blockdb_prod FROM SHARE blockdb_org.blockdb_share;
```

4. (Optional) Enable streams on critical tables:

```sql theme={null}
CREATE OR REPLACE STREAM block_stream ON TABLE blockdb_prod.public."0101_blocks_v1";
```

## Table Structure

* Column names and types match the SQL in `/BlockDb.Postgres.Tables.Public`.
* `_tracing_id`, `_created_at`, `_updated_at`, and verification columns are included for lineage.
* Each dataset sits in its own schema so you can apply RBAC at a granular level.

## Operational Tips

* Use Snowpipe or tasks to copy data from the shared tables into your production schema if you need transformations.
* Streams capture inserts/updates so you can power near-real-time analytics or downstream event buses.
* Monitor freshness by comparing `_updated_at` against the SLAs defined in [Access & SLA](/data-catalog/overview/access-and-sla).

<Callout icon="lightbulb" color="#3B82F6" iconType="regular">
  Pair the Snowflake share with your own reconciliation queries or [support@blockdb.io](mailto:support@blockdb.io) to validate `_tracing_id` samples before critical reporting runs.
</Callout>