Skip to main content
A connector is the object that owns a connection to a data source. Every dataset belongs to exactly one connector. Connectors hold credentials (managed for you), schema metadata, and the list of tables Summand has discovered.

​
Connector kinds

CSV

A file you upload from your machine. The connector wraps a single file as a single-table source.

PostgreSQL / MySQL / Snowflake

Direct, read-only connections to your warehouse. Tables are discovered at create time and refreshed on demand.

Azure SQL

Azure SQL Database and Managed Instance via the standard TDS protocol.

Delta Sharing

Databricks UniForm shares — Iceberg-backed for type-faithful, incremental refresh.

Fivetran

Managed connection to anything Fivetran supports (Databricks without UniForm, Redshift, Oracle, BigQuery, 300+ SaaS APIs). Summand reads Fivetran’s Parquet output.

​
What a connector stores

Credentials for database connectors live in AWS Secrets Manager — Summand never stores plaintext passwords or keys. For Fivetran, your source credentials never touch Summand servers at all (they go directly to Fivetran).

​
Visibility inheritance

If a connector is set to public or showcase, every dataset under it is readable by anyone (subject to the visibility’s content rules — showcase blocks raw rows, public allows them). Setting the connector back to private locks down all datasets at once, regardless of their individual visibility settings. Use this when you need to revoke anonymous access across an entire source quickly.

​
When to create a new connector

  • One file per project — upload as a new CSV connector for clean isolation.
  • One database — one connector for the whole DB; Summand handles per-table datasets internally.
  • Different credentials — if two parts of the same database need different access patterns, use two connectors.

​
Limits