Teradata
On-premises, Teradata Vantage on AWS/Azure/GCP.
Access mode: Read-only or read-write
Required information
| Field | Details |
|---|---|
| Host / IP | Teradata server FQDN or IP (COP/CMIC address for load balancing). |
| Port | Default 1025 (Teradata SQL gateway). |
| Database(s) | Teradata databases (logical groupings of tables). |
| Credentials | Username + password. LDAP auth if configured. |
| Access level | Read-only: SELECT on databases/tables, EXECUTE PROCEDURE. Read-write: add INSERT, UPDATE, DELETE. |
| Character set | Typically UTF8 or UTF16. Must match to avoid encoding issues. |
Network considerations
On-premises (most common): VPN or dedicated network circuit. Teradata clusters are rarely exposed to the internet.
Vantage on cloud: Available as managed service on AWS/Azure/GCP. Standard cloud networking (VPC peering, PrivateLink).
Unity Server: If using Teradata Unity for routing, provide the Unity server address instead of direct COP addresses.
Query Grid: If cross-system queries are needed, Teradata Query Grid config must include Flume’s access.
Credential and auth management
LDAP auth preferred in enterprise deployments. Provide LDAP mechanism and any required configuration.
Standard Teradata auth: Username + password. Password expiry controlled by DBA.
Session limits: Teradata enforces account-level session limits (MaxSessions). Confirm the service account has adequate session allocation.
Query Band: Flume sets a QueryBand (ApplicationName=Flume) for workload management identification. Confirm WLM rules won’t throttle us.
Stored procedure and logic access
Teradata stored procedures invoked with CALL. Require EXECUTE PROCEDURE privilege. Introspection via DBC.TablesV (filter TableKind = 'P') and SHOW PROCEDURE. Macro objects (TableKind = 'M') are also common in Teradata. Confirm whether macros are in scope.
Validation checks
| Check | Method | Expected result |
|---|---|---|
| Network reachability | telnet <host> 1025 | Connected |
| Authentication | SELECT 1; | Returns 1 |
| Identity | SELECT USER; | Expected service account |
| Database access | SELECT TableName FROM DBC.TablesV WHERE DatabaseName = '<db>' | Lists tables |
| Procedure listing | SELECT TableName FROM DBC.TablesV WHERE DatabaseName = '<db>' AND TableKind = 'P' | Lists procedures |
| Execute test | CALL <db>.<proc>(test_params); | Returns expected result |
| Permission audit | SELECT * FROM DBC.AllRightsV WHERE UserName = '<user>' | Matches expected rights |
Every connection starts from the pre-engagement checklist and goes through the universal validation protocol before production sign-off.