Teradata: projected connector

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.

Capability matrix

Teradata does not ship yet, so no capability is verified. The column shows what the design plans; plans are not commitments.

How the connector is designed to prove read-only access

Designed: DBC.AllRightsV shows only SELECT (R) rights for the connector user.

Design: a warehouse connector with bounded reads.

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.