Connect your warehouse

Give Single Origin read-only access to your metadata and query history.

Single Origin needs read access to two things: your object metadata (tables, views, columns) and your query or job history. It never needs to read the rows in your tables.

Pick your engine below. Each guide lists the exact grants, gives a script or Terraform you can run, and ends with what to send to your Single Origin contact.

EngineGuideHow Single Origin connectsWhat it reads
SnowflakeConnect to SnowflakeA dedicated role and service user with key-pair authenticationObject metadata and query and usage history from the SNOWFLAKE.ACCOUNT_USAGE views
DatabricksConnect to DatabricksA service principal with OAuth machine-to-machine authenticationUnity Catalog metadata: catalogs, schemas, tables, views, columns, comments, tags and lineage
BigQueryConnect to BigQueryIAM roles granted to a Single Origin service accountDataset, table, view, model and routine metadata, plus job and reservation metadata
Amazon RedshiftConnect to RedshiftA dedicated user and roleSystem tables and views, plus table and column definitions through REFERENCES
Apache Spark (open source)Connect to SparkParquet files you export and uploadTable, column and view metadata, Spark event logs, and optionally SQL text per application
Trino and PrestoConnect to TrinoA dedicated login with file-based access controlinformation_schema metadata and system.runtime query and task metadata

Before you start

  • Have an admin for the engine ready. Most guides need an account or metastore admin to grant metadata roles.
  • Ask your Single Origin contact for the values the guide needs, such as a public key or a service account address.
  • Plan for a small amount of compute. Most engines need a small warehouse or SQL endpoint to run the metadata queries.

After you connect

Send the details listed under Finish up in your guide to your Single Origin contact. Single Origin then starts loading your history. Continue with the Quickstart.

Removing access

Each guide ends with a Revoking access section. Dropping the role, user or service principal ends Single Origin's access at once.


Did this page help you?