Skip to main content
For AI agents: a documentation index is available at https://docs.coverbase.com/llms.txt. This page is also available in markdown by appending .md to the URL.
A Snowflake destination is part of warehouse data share. Coverbase connects through the Snowflake SQL API with key-pair authentication, creates one table per contract table on the first sync, and keeps a <table>_current view beside each.

Prepare Snowflake

  1. Create a key pair. Keep the private key (PEM) for Coverbase, and set the public key on the Snowflake user as RSA_PUBLIC_KEY.
  2. Give the user a role with:
    • USAGE on the warehouse, the database and the schema;
    • CREATE TABLE and CREATE VIEW on the schema.
  3. Use a schema of its own, so Coverbase’s tables and views do not mix with others.
The names are examples; use your own.

Add the destination in Coverbase

  1. Open Configuration → Data Share and click Add destination.
  2. Choose Snowflake, give it a Name, and choose Hourly or Daily.
  3. Enter the Account, User, Role, Warehouse, Database and Schema, paste the Private Key (PEM), and add the Key passphrase if the key has one.
  4. Click Add destination, then Test connection, then Sync now.
After saving, the card shows the key’s fingerprint as a hint. The private key is never shown again. Archiving the destination deletes it.

What lands in Snowflake

  • One table per contract table, created on the first sync. A column the contract adds later is added to the table.
  • Each sync appends the rows that changed, stamped with _cb_synced_at.
  • A <table>_current view per table keeps the newest version of each row. For the services snapshot table, it keeps only the latest run.
Point Power BI or Tableau at the _current views. The tables and their columns are listed under Table Contract on the Data Share page.

Data share guide

Run logs, pausing and the table contract.

BigQuery

The BigQuery destination.

Amazon S3

The S3 destination.

Integration credentials and signing

How the private key is stored.