modellerUpdated 2026-05-18

Add a Data Source

Model Builder — data source settings panel.

What this covers

Each Tessallite project connects to exactly one data source. This article explains how to view or change the data source connection from the project Settings panel, describes the connection parameters for each supported source type, and lists common connection failure causes and remedies.

Steps

  1. Open the project from the workspace dashboard.
  2. Click the Settings tab at the top of the project page.
  3. Locate the Data Source section. The current source type and connection parameters are shown.
  4. To change the source type, select a new type from the Source type dropdown and fill in the parameters.
  5. Click Test Connection to verify.
  6. Click Save to apply the change.
Warning: Changing the source type after tables have been added to the model will invalidate all table references. You must remove all existing tables and re-add them from the new source before the model can be used.

Connection parameter reference

PostgreSQL

ParameterRequiredNotes
HostYesHostname or IP of the PostgreSQL server.
PortYesDefault is 5432.
DatabaseYesThe database name containing your schemas and tables.
UserYesDatabase user with SELECT access on the target schemas.
PasswordYesStored encrypted; never shown in plain text after saving.

BigQuery

ParameterRequiredNotes
Project IDYesThe GCP project ID that owns the BigQuery dataset (e.g. my-gcp-project). This is stored in the connection credentials and used to qualify table names as project_id.dataset.table_name.
Service account JSONYesFull JSON key file. Account must have bigquery.dataViewer and bigquery.jobUser roles. For calendar auto-create, the account also needs bigquery.dataEditor.
Allow Tessallite to run DDLNoCheckbox under connection settings. Required for calendar auto-create. Without it, you must run the DDL manually and bind the table.

When adding a BigQuery source to a model, the Dataset field specifies which BigQuery dataset to expose. Tessallite uses the project ID from the connection credentials and the dataset from the source configuration to build fully qualified table references: project_id.dataset.table_name. Identifiers with hyphens (common in GCP project IDs like my-company-prod) are automatically backtick-quoted in generated SQL.

Amazon Redshift

ParameterRequiredNotes
HostYesRedshift cluster endpoint.
PortYesDefault is 5439.
DatabaseYesRedshift database name.
UserYesRedshift user with SELECT access.
PasswordYesStored encrypted; never shown in plain text after saving.

Uses the same asyncpg driver as PostgreSQL (Redshift is wire-compatible). No additional installation required.

Snowflake

ParameterRequiredNotes
AccountYesSnowflake account identifier (e.g. xy12345.us-east-1.aws).
UsernameYesSnowflake user.
PasswordYesStored encrypted; never shown in plain text after saving.
DatabaseYesSnowflake database name.
SchemaNoDefault schema. Defaults to PUBLIC.
WarehouseYesCompute warehouse for query execution.
RoleNoSession role (optional).

Requires snowflake-connector-python. See Supported Data Sources for installation instructions.

Hadoop / Spark Thrift Server

ParameterRequiredNotes
Thrift Server hostYesHostname or IP of the HiveServer2 or Spark Thrift Server endpoint.
PortYesDefault is 10000 for HiveServer2, 10001 for Spark Thrift Server.
DatabaseYesThe Hive or Spark database (schema) name.

SQL Server

ParameterRequiredNotes
HostYesHostname or IP of the SQL Server instance.
PortYesDefault is 1433.
DatabaseYesSQL Server database name.
UsernameYesSQL Server login.
PasswordYesStored encrypted; never shown in plain text after saving.
SchemaNoDefault schema. Defaults to dbo.
ODBC DriverNoDriver name. Defaults to ODBC Driver 17 for SQL Server.
EncryptNoEncrypt the connection to SQL Server using TLS.
Trust Server CertificateNoAccept self-signed certificates (non-production only).

Requires aioodbc and an ODBC driver installed on the host. See Supported Data Sources for driver installation instructions.

What Test Connection checks

The test asks the gateway to authenticate against the source using the parameters you entered. It confirms:

A successful test does not validate that specific schemas or tables exist.

Common connection failures

ErrorLikely causeRemedy
Connection timed outHost not reachable; firewall or VPC block.Allow the gateway's outbound IP through the source's firewall rules.
Connection refusedDatabase service not running on specified port, or wrong port.Verify port number and confirm the database service is running.
Authentication failedWrong credentials or expired service account key.Re-enter credentials. For BigQuery, generate a new key in the GCP console.
Database does not existMisspelled database name or user lacks access.Confirm the database name and access grant.
Permission deniedUser can connect but lacks SELECT on target schema.Grant SELECT on the relevant schemas and tables.

Schema search and filter

The table list in the Sources panel includes a search field that filters tables and columns as you type. This is useful when your source has hundreds of tables and you need to find a specific one.

Related