Teradata Reference Guide

Immuta policies will not be automatically enforced in Teradata

While you can author and apply subscription and data policies on Teradata data sources within Immuta, these policies will not be enforced natively in the Teradata platform. You can use Immuta webhooks to be notified about changes to user access and make appropriate access updates in Teradata using your own process.

In the Teradata connection, Immuta registers data from Teradata.

What does Immuta do in my Teradata environment?

Registering a connection

Immuta utilizes connections to register and manage data from your Teradata environment. Instead of registering individual databases, connections enable you to register an entire data platform at once. This approach simplifies data registration and allows Immuta to automatically monitor your Teradata platform for changes. Data sources are then added or removed to reflect the current state of your data platform.

When the connection is registered, Immuta ingests and stores connection metadata in the Immuta metadata database. In the example below, the Immuta application administrator connects the database that contains marketing-data , research-data , and cs-data views. Immuta registers these views as data sources and stores the view metadata in the Immuta metadata database. Creating the connection does not impact any user's existing access in Teradata.

Immuta presents a hierarchical view of your data that reflects the hierarchy of objects in Teradata after registration is complete:

• Host

• Database

• View

Beyond making the registration of your data more intuitive, connections provides more control. Instead of performing operations on individual schemas or views, you can perform operations (such as object sync) at the connection level.

See the Connections reference guide for details about connections and how to manage them. To configure your Teradata connection, see the Register a Teradata connection guide.

Teradata privileges

The privileges that the Teradata connection requires align to the least privilege security principle. The table below describes each privilege required by the and the user.

Teradata privilege	User requiring the privilege	Explanation
DBADMIN in Teradata	Setup user	This privilege allows the user registering the connection to assign SELECT privileges to the Immuta system account so that it can register and manage the connection.
SELECT on the DBC user	Immuta system account	This privilege provides access to all the Teradata system views necessary to register the connection and maintain state between the Teradata database and Immuta.

Maintaining state with Teradata

The following user actions spur various processes in the Teradata connection so that Immuta data remains synchronous with data in Teradata. The list below provides an overview of each process:

• Data source created: Immuta registers data source metadata and stores that metadata in the Immuta metadata database.

• Data source deleted: Immuta deletes the data source metadata from the metadata database.

Supported object types

Views are the only supported object type for Teradata. If a Teradata database does not contain any views, it will not be ingested into Immuta.

Security and compliance

Authentication method

The Teradata connection supports username and password authentication to register a connection. The credentials provided must be for an account with the permissions listed in the Register a Teradata connection guide.

Limitations and known issues

• The following Immuta features are unsupported:

  • Subscription and data policies

  • Identification

  • Tag ingestion

  • Query audit

• In the data source data dictionary, the column types will be unknown