> ## 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.

# Google BigQuery Archive Delivery

> Access BlockDB EVM blockchain datasets in Google BigQuery via Authorized Views or scheduled Transfer Service loads — no ETL required.

## Delivery Modes

| Mode                 | When to Choose                                                                   | How It Works                                                    |
| -------------------- | -------------------------------------------------------------------------------- | --------------------------------------------------------------- |
| **Authorized View**  | Need always-fresh tables without owning storage.                                 | BlockDB shares a dataset in its project; you query it directly. |
| **Transfer Service** | Want the data inside your own project for transformation or long-term retention. | Scheduled jobs copy tables/partitions into your project.        |

At launch, datasets `0101-0105` (ledger/execution) are GA; pricing datasets follow shortly.

## Onboarding Steps

1. Share your GCP project ID and region with [support@blockdb.io](mailto:support@blockdb.io).
2. For Authorized Views, grant BlockDB's service account `bigquery.dataViewer` on the consuming project. For Transfer Service, grant `bigquery.admin` on the target dataset or create a dedicated service account.
3. Confirm dataset list, chain coverage, and schedule (daily/hourly).
4. BlockDB configures the share or transfer job; you receive dataset names like `blockdb_prod.ledger_0101_blocks_v1`.

## Usage Patterns

* Join BlockDB tables with your proprietary data in BigQuery SQL; leverage `_tracing_id` for lineage.
* Export slices to GCS if you need to interop with other warehouses.
* Use scheduled queries or dbt to materialize curated marts downstream.

## Validation & Monitoring

* Compare row counts with the [Dataset Index](/data-catalog/evm/dataset-index) or manifest metadata delivered via auxiliary tables.
* Alert when `_updated_at` drifts from the SLAs in [Access & SLA](/data-catalog/overview/access-and-sla).
* For Transfer Service, monitor job status in Cloud Console and set up notifications for failures.

<Callout icon="lightbulb" color="#3B82F6" iconType="regular">
  If you require low-latency updates, combine BigQuery archive loads with REST API polling or streaming buckets described under [Real Time Channels](/user-guide/real-time-delivery/introduction).
</Callout>