Integrations · Data warehouses · Coming next
Teradata: coming next connector
Teradata Vantage connector using Teradata's driver installed by the customer: restricted dictionary-view discovery, declared primary keys (kept distinct from primary indexes), referential constraints, statistics-based estimates, bounded profiles and reads over verified TLS.
Coming next Data warehouses
Active implementation; not yet available for production use.
Customer-installed driver. The Teradata driver (teradatasql 20.0.0.69) is licensed by its vendor under the Teradata License Agreement, which does not allow DataNivra to redistribute it, so the standard agent image does not include it. You install it by building the agent extension image; building it means you accept that licence.
Not available yet. Active implementation; not yet available for production use. The console does not offer it, and asking an agent for a connector it does not ship fails with the error code CONNECTOR_NOT_AVAILABLE; the product never fakes a connection.
What you can do today
Export tables to Parquet or CSV inside your network and read them with the shipped Local files, Amazon S3 / S3-compatible or Azure Blob / Data Lake connectors.
Whatever route you choose, the export and every row-level step stay inside your network. You can evaluate the whole workflow now with the synthetic demo.
Known limitations
- Customer-installed driver: the standard agent image does not include teradatasql. Build the DataNivra agent extension image (agent/runtime/extensions/teradata), which installs teradatasql under the Teradata License Agreement that you accept; without it the agent reports CONNECTOR_NOT_AVAILABLE.
- A primary index is not a primary key: tables keyed only by a primary index need a declared PRIMARY KEY or a relationship mapping.
- Soft referential integrity (WITH NO CHECK OPTION) is reported but not enforced by Teradata.
- Not yet run against a real Teradata system (no free local engine).
Capability matrix
Teradata does not ship yet, so no capability is verified. The column shows what the design plans; plans are not commitments.
| Capability | Design intent |
|---|---|
| Discovery | Planned |
| Classification | Planned |
| Profiling | Planned |
| Masking | Planned |
| Deterministic masking | Planned |
| Entity-aware subsetting | Planned |
| Relationship preservation | Planned |
| Synthetic workflows | Not planned yet |
| Certification | Planned |
| Provisioning | Planned |
| CI/CD | Not planned yet |
| Evidence generation | Planned |
How the connector is designed to prove read-only access
Proven from DBC.AllRightsV (the user and PUBLIC) and DBC.AllRoleRightsV (the user's roles) before reading: only the SELECT right (R) is accepted on the source databases; execute rights are tolerated on Teradata system databases only, and the user's own database must not be a source.
Customer-installed driver: Teradata's licence for teradatasql does not allow DataNivra to redistribute it, so you build DataNivra's extension image, which installs the pinned driver on top of a released agent image and binds you to Teradata's licence. sslmode defaults to VERIFY-FULL (the driver's own PREFER default could fall back to an unencrypted session).
Planned authentication: TD2 user and password (secret reference); LDAP user and password (secret reference).
What crosses the boundary
Connectors run inside the agent in your network. Only metadata, aggregates and evidence reach DataNivra Cloud:
- Schema, table and column names and data types (for file sets, operator-declared or opaque table names — never data-derived file names).
- Aggregates such as row-count estimates, null and distinct ratios; counts from 1 to 10 are reported as 10 (small-cell protection).
- Classification findings (which column looks like which kind of sensitive data) and relationship metadata.
- Evidence metadata: checksums, gate outcomes, engine and policy versions, and templated error codes.
Never sent:
- Any cell value, row, sample, minimum/maximum or top-k value — masked or not.
- Credentials, connection strings or resolved secret values: DataNivra stores only the secret reference.
- Free text copied from your data, or exception messages that contain values.
See the customer-resident architecture and how to verify these claims yourself.
Request this connector
We prioritise connectors by demand, engineering effort and strategic fit. Telling us that Teradata matters to you is counted; it does not commit a delivery date.
Need something specific from the Teradata connector? Request a feature (please describe it without real data).
All integrations · Data warehouse test data management · Guides · Start free