Connect to and manage Teradata in Azure Purview
This article outlines how to register Teradata, and how to authenticate and interact with Teradata in Azure Purview. For more information about Azure Purview, read the introductory article.
Supported capabilities
| Metadata Extraction | Full Scan | Incremental Scan | Scoped Scan | Classification | Access Policy | Lineage |
|---|---|---|---|---|---|---|
| Yes | Yes | No | Yes | No | No | Yes* |
* 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, Azure Purview supports:
Extracting technical metadata including:
- Server
- Databases
- 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).
Prerequisites
An Azure account with an active subscription. Create an account for free.
An active Azure Purview resource.
You will need to be a Data Source Administrator and Data Reader to register a source and manage it in the Azure Purview Studio. See our Azure Purview Permissions page for details.
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 virtual machine where the self-hosted integration runtime is installed.
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.
You will have to manually download Teradata's JDBC Driver on your virtual machine where self-hosted integration runtime is running. The executable JAR file can be downloaded from the Teradata website.
Note
The driver should be accessible to all accounts in the VM. Please do not install in a user account.
Register
This section describes how to register Teradata in Azure Purview using the Azure Purview Studio.
Authentication for registration
The only supported authentication for a Teradata source is Basic authentication. Make sure to have Read access to the Teradata source being scanned.
Steps to register
Navigate to your Azure Purview account.
Select Data Map on the left navigation.
Select Register
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 or a fully qualified connection string to the server.
Select a collection or create a new one (Optional)
Finish to register the data source.
Scan
Follow the steps below to scan Teradata to automatically identify assets and classify your data. 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 is not 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 Azure Purview Studio.
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 are not acceptable
Driver location: Specify the path to the JDBC driver location in your VM where self-host integration runtime is running. This should be the path to valid JAR folder location.
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.
Note
As a rule of thumb, please provide 2GB memory for every 1000 tables
Select Continue.
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, do the following:
Go to the Azure Purview Studio. Select the Data Map tab under the left pane.
Select the desired data source. You will see a list of existing scans on that data source under Recent scans, or can view all scans under the Scans tab.
Select the scan that has results you want to view.
This page will show you all of the previous scan runs along with the status and metrics for each scan run. It will also display whether your scan was scheduled or manual, how many assets had classifications applied, how many total assets were discovered, the start and end time of the scan, and the total scan duration.
Manage your scans - edit, delete, or cancel
To manage or delete a scan, do the following:
Go to the Azure Purview Studio. Select the Data Map tab under the left pane.
Select the desired data source. You will see a list of existing scans on that data source under Recent scans, or can view all scans under the Scans tab.
Select the scan you would like to manage. You can edit the scan by selecting Edit scan.
You can cancel an in progress scan by selecting Cancel scan run.
You can delete your scan by selecting Delete scan.
Note
- 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 in the schema tab of Azure Purview.
Lineage
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.
Next steps
Now that you have registered your source, follow the below guides to learn more about Azure Purview and your data.