Create a Teradata metadata collector

Create a collector to import metadata from Teradata.

Before you begin

• A MID Server is set up for the collectors. For more information, see MID Server for metadata collectors.
• All prerequisite tasks are complete. For more information, see Prepare to run the Teradata Collector.

Role required: connection-admin or admin.

Procedure

1. Navigate to All > Workflow Data Fabric > Workflow Data Fabric Home.
2. Select the Connect Hub icon in the left sidebar.
3. Select Create > Metadata collector.
4. From the System list, select Teradata.
5. From the Connection type list, select one of the following:
   1. Select New connection to configure a new connection.
   2. Select Existing connection to reuse an existing connection and select an existing connection from the Connections list.
      The configuration form is filled with details from the existing connection. The name is appended with the word Copy and sensitive details like password aren't copied.
6. Complete the form.

   Table 1. Teradata metadata collector form

   Field	Description
   Connection name	Unique identifier for the connection. This field can't be modified once the connection is established.
   Short description	Purpose and details of the connection.

7. Configure the connection properties.

   Table 2. Connection options

   Field	Description
   Server	Hostname of the database server to connect to.
   Server port	Port of the database server, if not the default.

8. Configure the authentication options.

   Table 3. Authentication options

   User name	Username for authenticating with the database server.
   Password	Password for authenticating with the database server.

9. Configure the database options.

   Table 4. Configuration options

   Include databases	Name of the database to connect to. To add multiple databases, select Add. Note: If this property is not specified, the collector harvests metadata from all databases. Use the optional Excluded databases parameter to exclude specific databases.
   Excluded databases	Regular expressions indicating databases not to catalog. Use when the Include databases parameter is not set — the collector then harvests metadata from all databases, and this parameter excludes specific ones. Note: This parameter is ignored if the Include databases parameter is specified. To use Excluded databases, do not set the Database parameter.

10. Configure the advanced options.

    Table 5. Advanced options

    Enable column statistics collection	Whether to enable harvesting of column statistics, that is, data profiling. Note: Enabling this feature may extend the running time of the collector because the collector requires access to table data to gather profiling metadata.
    Target sample size for column statistics	Target number of rows to sample from tables.
    Disable lineage collection	Whether to skip harvesting of intra-database lineage metadata.
    Disable extended metadata collection	Whether to skip harvesting of extended metadata for resource types such as database, schema, table, columns, functions, stored procedures, user-defined types, and synonyms. Basic metadata for these resource types is still harvested.
    Exclude system functions	Whether to exclude system functions.
    Server environment	Friendly name for the environment in which the database server runs. Use this field when the server name is localhost to differentiate it from other environments.
    Database ID	Unique identifier for this database, used to generate the ID for the database. Provide this value only if the database name used for the connection does not uniquely identify the database.
    JDBC properties	JDBC driver properties to pass to the driver connection, in name=value format.
    SQL parsing timeout	Timeout in seconds for SQL parsing during lineage collection. The default is 60.

11. Select Save.

Result

The metadata collector is created and appears on the Connectors page with a Configured status. The collector is ready to connect to the source system and harvest metadata.

What to do next

After the collector is created, perform any of the following tasks:

• Run the collector manually to harvest metadata immediately. See Run metadata collectors manually.
• Automate metadata collection by scheduling regular collector runs. See Schedule metadata collector runs.
• Monitor execution status and troubleshoot issues by viewing the runtime logs. See View runtime logs for collector runs.
• Discover and evaluate the harvested data assets in the Data Catalog. See Governing the Data Catalog.