analystUpdated 2026-07-02

JDBC Connection Guide

DBeaver New Database Connection dialog (PostgreSQL).

What this covers

Tessallite exposes a PostgreSQL wire-protocol endpoint on port 5433. Any JDBC client that supports the standard PostgreSQL driver can connect — including DBeaver, Tableau, and any tool using psycopg2 or the JDBC PostgreSQL driver. No Tessallite-specific driver is required.

This article is a detailed connection reference. For a shorter walkthrough, see Connect a BI Tool via JDBC.

Connection parameters

ParameterValueNotes
HostHostname or IP of the Tessallite GatewayUse localhost for local installs. Obtain from your System Admin for cloud deployments.
Port5433Fixed. Not the standard PostgreSQL port (5432).
DatabaseWorkspace slug, optionally with a model or project (e.g., acme, acme/sales, acme/finance/sales)Case-sensitive. This is not a real database name — it routes to the correct workspace and, optionally, scopes the connection to one model. See "Scoping to one model or project" below.
UsernameYour Tessallite email address
PasswordYour Tessallite password
SSLOptional for generic JDBC clients; required for the supported Looker pathAdd ?sslmode=require for Looker or whenever the server requires SSL.
Driver classorg.postgresql.DriverStandard PostgreSQL JDBC driver. No Tessallite-specific driver needed.

JDBC URL format

jdbc:postgresql://HOST:5433/WORKSPACE_SLUG

Example:

jdbc:postgresql://analytics.example.com:5433/acme

With SSL:

jdbc:postgresql://analytics.example.com:5433/acme?sslmode=require
The "database" field must contain the workspace slug, not a real database name. Entering anything else returns FATAL: database "X" does not exist.
Looker Studio/Data Studio direct uses this standard PostgreSQL wire path and does not require generated LookML or LOOKER_GATEWAY_ENABLED. That flag controls only the optional generated relation surface for Looker-hosted use.

Scoping to one model or project

By default the Database field takes just the workspace slug, and the connection browses every published model in the workspace as a separate table. To open the connection directly on one model, add it to the Database field:

FormExampleScope
WORKSPACE_SLUGacmeEvery published model in the workspace
WORKSPACE_SLUG/MODEL_SLUGacme/salesOne model
WORKSPACE_SLUG/PROJECT_SLUG/MODEL_SLUGacme/finance/salesOne model, disambiguated by project — use this form when two projects have a model with the same name

The scoped forms are useful when a workspace has many models and you only need one, or when you are connecting a tool (such as Superset or a hand-written script) to a single dataset. If the model or project you name does not exist, the connection is refused immediately with a message listing the accepted formats — you will not get a confusing error later when you run a query.

Connect with DBeaver

  1. Open DBeaver.
  2. Click New Database Connection (plug icon in toolbar).
  3. Select PostgreSQL and click Next.
  4. Fill in Host, Port (5433), Database (workspace slug, or workspace/model to scope to one model), Username, and Password.
  5. Click Test Connection. A "Connected" dialog confirms success.
  6. Click Finish.
  7. Expand the connection in the left panel to see schemas and columns.

Connect with Tableau

  1. Open Tableau Desktop.
  2. In the Connect pane, under To a Server, select PostgreSQL.
  3. Enter the Gateway hostname in Server.
  4. Enter 5433 in Port.
  5. Enter the workspace slug in Database.
  6. Enter your credentials and click Sign In.

Connect with Apache Superset

  1. Log in to Superset.
  2. Go to Data > Databases > + Database.
  3. Select PostgreSQL as the database type.
  4. In the SQLAlchemy URI field, enter: postgresql://USER:PASSWORD@HOST:5433/WORKSPACE_SLUG — replace with your Tessallite credentials and gateway address.
  5. Click Test Connection to verify.
  6. Click Connect.
  7. Navigate to SQL Lab to run queries against Tessallite models, or create datasets from the connection for use in charts and dashboards.

Superset connects via the standard PostgreSQL driver (psycopg2). No additional driver installation is needed.

Driver note

Tessallite uses the PostgreSQL wire protocol. Use the standard org.postgresql.Driver (JDBC) or psycopg2 (Python). No special driver is required.

For PostgreSQL and Redshift sources, a valid query that returns no rows still returns its declared result columns to the JDBC gateway. Empty and non-empty results therefore have the same column shape. Use explicit SQL aliases when a portable result name is important across source engines.

Troubleshooting

SymptomLikely causeResolution
Connection refused on port 5433Gateway not running or wrong hostVerify Gateway service is up with your System Admin
FATAL: database "X" does not existWrong workspace slugVerify slug with Tenant Admin (case-sensitive)
Unknown model 'X' in ... or Invalid database name at connect timeModel or project slug in a scoped Database field is wrongCheck the model/project slugs with your Modeller; the error message lists the accepted formats
Authentication failedWrong username or passwordUse Tessallite email and password, not source DB credentials
SSL errorServer requires SSLAppend ?sslmode=require to the JDBC URL
No tables visibleNo published modelsA Modeller must publish at least one model
New columns or tables missing after a model was just publishedYour tool read the catalogue once when it connected, so a mid-session publish is not visible yetDisconnect and reconnect the connection in your BI tool; the refreshed catalogue then shows the new model
A generated LookML relation reports support disabledOptional Looker adapter is default-offEnable LOOKER_GATEWAY_ENABLED=true only when validating a Looker-hosted project

Related