--- sourceDocument: Australia Workflow Data Fabric sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications Release : - australia ft:locale : - en-US ft:publication_title : - Australia Workflow Data Fabric ft:clusterId : - crint bundleId : - crint workflow : - Creator --- # Teradata metadata collector # Teradata metadata collector {#ariaid-title1} Release version: Australia Updated June 18, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Teradata Metadata Collector The Teradata Metadata Collector is a tool designed to harvest read-only metadata from a Teradata database account. It captures detailed metadata about various Teradata objects such as user defined functions, stored procedures, triggers, user defined types, and methods. The collector connects to Teradata using username and password authentication, requiring a dedicated database user with appropriate permissions to run. Show full answer Show less ## Key Features * **Metadata Cataloged:** The collector gathers extensive metadata including database types, tables, indexes, schemas, views, user defined functions, stored procedures (SQL and external), triggers, user defined types, and methods. Metadata details include creation and modification information, descriptions, keys, sizes, and definitions. * **Profiling and Sampling:** If enabled, the collector also harvests column-level profiling data such as average/max/min values, data distribution, distinct values, sample strings, and row counts. This requires read access to the actual data. * **Relationships and Lineage:** The harvested metadata automatically includes relationships between resources like tables, columns, indexes, triggers, schemas, and databases. It captures lineage information for views and stored procedures, identifying data sources, sorting, filtering, aggregation, and downstream table updates, with some limitations on certain SQL constructs. ## Practical Considerations for ServiceNow Customers * **Authentication Setup:** Before running the collector, create a dedicated Teradata user with necessary permissions to ensure secure and successful metadata harvesting. * **Collector Creation:** Configure the Teradata Metadata Collector in your ServiceNow environment to import metadata effectively from your Teradata database. * **Data Profiling Access:** Ensure users or roles have read privileges on Teradata data to enable profiling and sampling features for richer metadata insights. * **Lineage Limitations:** Be aware that lineage extraction does not support SQL statements with variable-defined queries, SELECT INTO clauses, multiple inserts in stored procedures, or transient table creation within stored procedures. ## Benefits Enabling the Teradata Metadata Collector allows ServiceNow customers to gain comprehensive visibility into their Teradata environment's metadata, understand data relationships and lineage, and enhance data governance, impact analysis, and compliance efforts. This detailed metadata foundation supports better data management and informed decision-making. The Teradata metadata collector harvests read-only metadata from a Teradata account. The collector harvests metadata from Teradata, including user defined functions, stored procedures, triggers, user defined types, and user defined methods. ## Authentication supported {#teradata-metadata-collector__section_k5s_q2c_qjc} The collector authenticates to Teradata using [username and password](https://docs.teradata.com/r/ODBC-Driver-for-Teradata-User-Guide/June-2022/Network-Security/Authentication-Mechanisms). Before running the collector, set up a dedicated database user with the required permissions. See [Prepare to run the Teradata Collector](https://www.servicenow.com/docs/Ujie64qgrJi_nGbrj5TOLw "Create a dedicated Teradata user with the permissions required for the metadata collector to harvest metadata from a target database."). ## Metadata cataloged {#teradata-metadata-collector__section_kbz_q2c_qjc} {#teradata-metadata-collector__table_dw4_fmc_qjc__entry__2} | Object | Information cataloged | |-|-| | Database | Type, Name, JDBC URL Extended metadata: Created By, Created At, Updated By, Updated At, Owner name, Space allocation (permanent, spool, temporary), Description | | Table | Name, Description, Primary Key, Foreign Key, Sample rows (if data sampling is enabled) Extended metadata: Created By, Created At, Updated By, Updated At, Size | | Table index | Index Cardinality, Column name, Index Type, Index Name, Is Non Unique, Column Ordinal Position, Pages, Column Sort Sequence | | Schema | Name | | Column | Name, Description, Data Type, Is Nullable | | View | Name, Description, SQL definition, Created By, Created At, Updated By, Updated At | | User defined functions | Name, Function type Extended metadata: Definition, Deterministic characteristic, Null-call characteristic, Description, Number of parameters, Source file language, Data access, Parameter style, Execution protection mode, Platform type, Character type, Created, Created By, Last Modified, Last Modified By, External File Reference | | SQL stored procedures | Name, Description, Stored procedure type, Definition Extended metadata: Created, Created By, Last Modified, Last Modified By | | External stored procedures | Name, Stored procedure type Extended metadata: Definition, Application category, Description, Number of parameters, External file reference, Execution protection mode, Character type, Platform type, Source file language, Parameter style, Data access | | Triggers | Name, Fired at instant Extended metadata: Created By, Created At, Updated By, Updated At, Name, Evaluation type, Fired on event, Trigger enabled, Order number, Definition, Trigger Comment, Subject Table Name, Action Time, Trigger Definition | | User defined types | Extended metadata: Name, Type, Default transform group, Ordering form, Ordering Category, Default null specified for array, All operators supported, Encryption supported, Compression supported, Instantiable, Final | | User defined methods | Name, Description, Number of parameters, Source file language, Data access, Parameter style, Deterministic characteristic, Null-call characteristic, Execution protection mode, Character type, Platform type | [Table 1. Teradata metadata cataloged by object type] {#teradata-metadata-collector__table_dw4_fmc_qjc} Profiling and sampling specific information.{#teradata-metadata-collector__section_kbz_q2c_qjc-profiling} If you include the profiling and sampling specific parameters while running the collector, the following additional information is harvested for columns. Note: Users or roles must have read access to data to harvest profiling information (column statistics). {#teradata-metadata-collector__table_ew4_fmc_qjc__entry__2} | Object | Information cataloged | |-|-| | Column | * Average Length (sample) * Average Value (sample) * Data Distribution * Distinct Values * Estimated Distinct Values * Estimated Non-null Values * Maximum Length (sample) * Maximum Value (sample) sorted numerically or alphabetically (z--a) * Minimum Length (sample) * Minimum Value (sample) sorted numerically or alphabetically (a--z) * Non-null Values (sample) * Sample String Values (first 5 items in a column) {#teradata-metadata-collector__ul_fw4_fmc_qjc} | | Table | * Row Count * Sample Count (target sample size) {#teradata-metadata-collector__ul_gw4_fmc_qjc} | [Table 2. Profiling and sampling metadata cataloged by object type] {#teradata-metadata-collector__table_ew4_fmc_qjc} ## Relationships between objects {#teradata-metadata-collector__section_bz3_r2c_qjc} By default, the harvested metadata includes catalog pages for the following resource types. Each catalog page has a relationship to the other related resource types. If the metadata presentation for this data source has been customized, you might see other resource pages and relationships.{#teradata-metadata-collector__section_bz3_r2c_qjc-intro} {#teradata-metadata-collector__table_hw4_fmc_qjc__entry__2} | Resource page | Relationship | |-|-| | Table | * Columns contained in tables * Table indexes {#teradata-metadata-collector__ul_iw4_fmc_qjc} | | Columns | * Table * Table indexes {#teradata-metadata-collector__ul_jw4_fmc_qjc} | | Table indexes | Columns | | Trigger | Table triggers on tables | | Schema | * Database that contains schema * Table that is part of schema {#teradata-metadata-collector__ul_kw4_fmc_qjc} | | Database | Schema contained in database | [Table 3. Teradata resource page relationships] {#teradata-metadata-collector__table_hw4_fmc_qjc} ## Lineage for Teradata {#teradata-metadata-collector__section_n5p_r2c_qjc} The Teradata collector collects the following lineage information.{#teradata-metadata-collector__section_n5p_r2c_qjc-intro} Note: Lineage for SQL statements defined via variable statements is not supported. {#teradata-metadata-collector__table_lw4_fmc_qjc__entry__2} | Object | Lineage available | |-|-| | View | The collector identifies the associated column in an upstream view or table: * Where the data is sourced from * That sort the rows via ORDER BY * That filter the rows via WHERE/HAVING * That aggregate the rows via GROUP BY {#teradata-metadata-collector__ul_mw4_fmc_qjc} | | Stored procedure | The collector identifies: * The associated column in an upstream view or table * Where the data is sourced from * That sort the rows via ORDER BY * That filter the rows via WHERE/HAVING * That aggregate the rows via GROUP BY * The downstream table that has its data updated {#teradata-metadata-collector__ul_nw4_fmc_qjc} Lineage is not available in the following cases: * The SQL statement in stored procedures contains the SELECT INTO clause * Stored procedures with multiple insert statements * Stored procedures used to create tables or transient tables created during the execution scope of a stored procedure {#teradata-metadata-collector__ul_ow4_fmc_qjc} | [Table 4. Teradata lineage by object type] {#teradata-metadata-collector__table_lw4_fmc_qjc} * **[Prepare to run the Teradata Collector](https://www.servicenow.com/docs/Ujie64qgrJi_nGbrj5TOLw)** Create a dedicated Teradata user with the permissions required for the metadata collector to harvest metadata from a target database. * **[Create a Teradata metadata collector](https://www.servicenow.com/docs/G8HjdfzZPTp2qrE63fQZbA)** Create a collector to import metadata from Teradata.