Connect to and manage Teradata in Microsoft Purview
This article outlines how to register Teradata, and how to authenticate and interact with Teradata in Microsoft Purview. For more information about Microsoft Purview, read the introductory article.
|Metadata Extraction||Full Scan||Incremental Scan||Scoped Scan||Classification||Access Policy||Lineage||Data Sharing|
* Besides the lineage on assets within the data source, lineage is also supported if dataset is used as a source/sink in Data Factory or Synapse pipeline.
The supported Teradata database versions are 12.x to 17.x.
When scanning Teradata source, Microsoft Purview supports:
Extracting technical metadata including:
- Tables including the columns, foreign keys, indexes, and constraints
- Views including the columns
- Stored procedures including the parameter dataset and result set
- Functions including the parameter dataset
Fetching static lineage on assets relationships among tables, views and stored procedures.
When setting up scan, you can choose to scan an entire Teradata server, or scope the scan to a subset of databases matching the given name(s) or name pattern(s).
Required permissions for scan
Microsoft Purview supports basic authentication (username and password) for scanning Teradata. The Teradata user must have read access to system tables in order to access advanced metadata. For classification, user also needs to have read permission on the tables/views to retrieve sample data.
To retrieve data types of view columns, Microsoft Purview issues a prepare statement for
select * from <view> for each of the view queries and parse the metadata that contains the data type details for better performance. It requires the SELECT data permission on views. If the permission is missing, view column data types will be skipped.
An Azure account with an active subscription. Create an account for free.
An active Microsoft Purview account.
You need Data Source Administrator and Data Reader permissions to register a source and manage it in the Microsoft Purview governance portal. For more information about permissions, see Access control in Microsoft Purview.
Set up the latest self-hosted integration runtime. For more information, see the create and configure a self-hosted integration runtime guide.
Ensure JDK 11 is installed on the machine where the self-hosted integration runtime is installed. Restart the machine after you newly install the JDK for it to take effect.
Ensure Visual C++ Redistributable for Visual Studio 2012 Update 4 is installed on the self-hosted integration runtime machine. If you don't have this update installed, you can download it here.
Download the Teradata JDBC driver on the machine where your self-hosted integration runtime is running. Note down the folder path which you will use to set up the scan.
The driver should be accessible by the self-hosted integration runtime. By default, self-hosted integration runtime uses local service account "NT SERVICE\DIAHostService". Make sure it has "Read and execute" and "List folder contents" permission to the driver folder.
This section describes how to register Teradata in Microsoft Purview using the Microsoft Purview governance portal.
Steps to register
Navigate to your Microsoft Purview account.
Select Data Map on the left navigation.
On Register sources, select Teradata. Select Continue
On the Register sources (Teradata) screen, do the following:
Enter a Name that the data source will be listed with in the Catalog.
Enter the Host name to connect to a Teradata source. It can also be an IP address of the server.
Select a collection or create a new one (Optional)
Finish to register the data source.
Follow the steps below to scan Teradata to automatically identify assets. For more information about scanning in general, see our introduction to scans and ingestion.
Create and run scan
In the Management Center, select Integration runtimes. Make sure a self-hosted integration runtime is set up. If it isn't set up, use the steps mentioned here to set up a self-hosted integration runtime
Select the Data Map tab on the left pane in the Microsoft Purview governance portal.
Select the registered Teradata source.
Select New scan
Provide the below details:
Name: The name of the scan
Connect via integration runtime: Select the configured self-hosted integration runtime.
Credential: Select the credential to connect to your data source. Make sure to:
- Select Basic Authentication while creating a credential.
- Provide a user name to connect to database server in the User name input field
- Store the database server password in the secret key.
To understand more on credentials, refer to the link here
Schema: List subset of databases to import expressed as a semicolon separated list. For Example:
schema1; schema2. All user databases are imported if that list is empty. All system databases (for example, SysAdmin) and objects are ignored by default.
Acceptable database name patterns using SQL LIKE expressions syntax include using %. For example:
A%; %B; %C%; D
- Start with A or
- End with B or
- Contain C or
- Equal D
Usage of NOT and special characters aren't acceptable
Driver location: Specify the path to the JDBC driver location in your machine where self-host integration runtime is running, e.g.
D:\Drivers\Teradata. It's the path to valid JAR folder location. Make sure the driver is accessible by the self-hosted integration runtime, learn more from prerequisites section.
Stored procedure details: Controls the number of details imported from stored procedures:
- Signature: The name and parameters of stored procedures.
- Code, signature: The name, parameters and code of stored procedures.
- Lineage, code, signature: The name, parameters and code of stored procedures, and the data lineage derived from the code.
- None: Stored procedure details aren't included.
Maximum memory available: Maximum memory (in GB) available on customer's VM to be used by scanning processes. This is dependent on the size of Teradata source to be scanned.
As a rule of thumb, please provide 2GB memory for every 1000 tables
Select a scan rule set for classification. You can choose between the system default, existing custom rule sets, or create a new rule set inline.
Choose your scan trigger. You can set up a schedule or ran the scan once.
Review your scan and select Save and Run.
View your scans and scan runs
To view existing scans:
- Go to the Microsoft Purview governance portal. Select the Data map tab on the left pane.
- Select the desired data source. You can view a list of existing scans on that data source under Recent scans, or you can view all scans on the Scans tab.
- Select the scan that has results you want to view. The page shows you all of the previous scan runs, along with the status and metrics for each scan run.
- Click the run ID to check more about the scan run details.
Manage your scans - edit, delete, or cancel
To manage or delete a scan:
Go to the Microsoft Purview governance portal. Select the Data Map tab on the left pane.
Select the desired data source. You can view a list of existing scans on that data source under Recent scans, or you can view all scans on the Scans tab.
Select the scan that you want to manage. You can then:
- Edit the scan by selecting Edit scan.
- Cancel an in-progress scan by selecting Cancel scan run.
- Delete your scan by selecting Delete scan.
- Deleting your scan does not delete catalog assets created from previous scans.
- The asset will no longer be updated with schema changes if your source table has changed and you re-scan the source table after editing the description on the Schema tab of Microsoft Purview.
After scanning your Teradata source, you can browse data catalog or search data catalog to view the asset details.
Go to the asset -> lineage tab, you can see the asset relationship when applicable. Refer to the supported capabilities section on the supported Teradata lineage scenarios. For more information about lineage in general, see data lineage and lineage user guide.
Now that you've registered your source, follow the below guides to learn more about Microsoft Purview and your data.
Submit and view feedback for