Skip to content

teradata.mdx

Latest commit

 

History

History
84 lines (56 loc) · 4.15 KB

teradata.mdx

File metadata and controls

84 lines (56 loc) · 4.15 KB
Raw
title Teradata
description Browsing databases and objects on Teradata Vantage, with TLS and transaction mode

import RegistryPlugin from "/snippets/registry-plugin.mdx";

Port 1025 carries a plain session. Any SSL mode moves the session to 443, where it runs over the gateway's WebSocket endpoint, and that port cannot be changed. A native Swift driver handles both, with no client library to install.

Teradata connection form

Teradata connection form

Quick setup

Click New Connection…, select Teradata, enter the host, username, and password, and click Save & Connect. Any Vantage system that accepts a TD2 logon works; no version is checked.

Connection settings

Field Description
Host Teradata database hostname
Port Plain gateway port, default 1025
Database Default database after logon. Optional; empty uses your account's default
Username / Password Teradata credentials
Logon Mechanism Options section. TD2 or TDNEGO, uppercase. Default TD2
Transaction Mode Options section. DEFAULT, ANSI, or TERA, uppercase
SSL Mode Network tab. Disabled by default

Leave Transaction Mode on DEFAULT, which takes whatever the system is configured for, unless a script needs ANSI or TERA case sensitivity and commit rules on the session. A system reachable only through a bastion works over an SSH tunnel.

Connection URL

teradata://user:password@host:1025/database

Import from URL… accepts the scheme; macOS does not route teradata:// links. See Connection URL Reference.

Databases and objects

A database and a user are both namespaces in Teradata, and both appear as top-level databases in the sidebar with their tables and views inside. A tab bound to a second database keeps the same session: DATABASE "name" runs ahead of its statements instead of a reconnect.

Identifiers are quoted with double quotes. Teradata has no LIMIT, so a table's first page comes back with TOP and later pages with QUALIFY ROW_NUMBER().

SSL/TLS

Mode What happens
Disabled Plain session on the gateway port
Preferred TLS on 443, falling back to a plain session on 1025 when the HTTPS port is unreachable
Required (skip verify) TLS, certificate not checked
Verify CA Certificate chain checked against the file in CA Certificate, hostname not checked. Refused without a CA certificate
Verify Identity Chain and hostname checked, against CA Certificate when set and the system trust store otherwise

A CA Certificate path that does not hold a readable certificate refuses the connection in both verify modes.

Test TLS on Required (skip verify) rather than Preferred, or a failed handshake looks like a successful connect.

Limitations

  • Foreign keys are never listed. The Structure tab's Foreign Keys section stays empty for Teradata; read the constraints from its DDL tab instead.
  • Macros and stored procedures are not in the sidebar. Query them from the editor.
  • LDAP, Kerberos, and JWT logon fail before the connect is attempted. Use TD2 or TDNEGO.
  • The TLS port is fixed at 443.

Troubleshooting

unsupported: logon mechanism …; only TD2 and TDNEGO are supported

Logon Mechanism holds something the driver does not implement. Set it to TD2 or TDNEGO. A value the driver does not recognize, a mechanism typed in lowercase included, is read as TD2 instead.

Cannot reach the server

The connect gives up when the connection's Connect timeout expires; an empty field under Options uses 30 seconds. Confirm the host, and that port 1025 is open from your network, or 443 if an SSL mode is set.

Logon fails

Check the username and password, and that the account is not locked.