--- 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 --- # Snowflake metadata collector # Snowflake metadata collector {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 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 Snowflake metadata collector The Snowflake metadata collector provides read-only access to metadata from an external Snowflake account, enabling ServiceNow customers to harvest comprehensive metadata from the Snowflake Data Cloud. It collects details on tables, views, materialized views, functions, stored procedures, policies, tags, data quality artifacts, and Streamlit applications, supporting enhanced visibility and governance of Snowflake data assets. Show full answer Show less ## Metadata Cataloged The collector catalogs extensive metadata, including: * **Tables, Views, and Materialized Views:** Names, comments, schema, ownership, creation and modification dates, extended attributes (e.g., transient, dynamic), and external URLs for direct access. * **Columns:** Names, data types, comments, key types, nullability, default values, and profiling statistics such as data distribution and sample values (when profiling is enabled). * **User-Defined Functions and Stored Procedures:** Full definitions, comments, signatures, language, runtime versions, ownership, and all overloaded versions. * **Schemas and Databases:** Identifiers, names, comments, creation and update dates, server details, environment, and connection URLs. * **Snowflake-Specific Artifacts:** Row access policies, masking policies, tags, and data metric functions with related metadata and relationships. * **Streamlit Applications:** App names, titles, descriptions, main file locations, creation dates, and owners. ## Relationships and Lineage The collector creates rich catalog pages linking related data assets, such as: * Relationships between tables, columns, tags, policies, views, materialized views, schemas, and Streamlit apps. * Lineage tracing from view columns to source table columns, covering ordering, filtering, and aggregation operations. * Dependencies among tables, views, functions, and stored procedures using Snowflake's OBJECTDEPENDENCIES view. * Stored procedure lineage indicating data sources and downstream tables updated, with some limitations (e.g., multitable inserts not supported). ## Additional Harvested Information When enabled, the collector also gathers: * **Column profiling and sampling data:** Statistics like average length, distinct values, max/min values, and sample strings. * **Snowflake policy and tag information:** Details about masking policies, row access policies, and tag values. * **Table usage metrics:** Query counts based on defined lookback periods. * **Data metric functions:** Function definitions, schedules, observations, and metrics. * **Streamlit app metadata:** Application identifiers, descriptions, owners, and file locations. ## Preparation and Setup To use the Snowflake metadata collector, ServiceNow customers must configure authentication and assign the necessary Snowflake roles and permissions to enable metadata harvesting. After setup, they can create a collector instance within ServiceNow to import Snowflake metadata and integrate it into their data catalog and governance processes. The Snowflake metadata collector provides read-only access to metadata from an external Snowflake account. The collector harvests metadata from Snowflake Data Cloud. It collects tabular objects, Horizon objects such as policies and tags, and Snowflake data quality artifacts. It also harvests functions and stored procedures. The collector can gather column statistics and table query counts. In addition, it can harvest metadata for Streamlit applications. ## Metadata cataloged {#snowflake-metadata-collector__section_cjt_2qh_phc} The Snowflake collector catalogs the following information. Note: The collector harvests all versions of overloaded functions and stored procedures. Each version has its own title/name in the catalog, but a distinct identifier. {#snowflake-metadata-collector__table_wtx_nqh_phc__entry__2} | Object | Information cataloged | |-|-| | Column | Name, Comments, Data Type, Is Nullable, Default Value, Key type (Primary, foreign) | | Table | Name, Comments, Primary key, Schema, External URL (Snowsight) Extended metadata: Is Iceberg, Is dynamic, Is transient, Created Date, Last Modified Date, Last Updated By (Snowflake LAST_DDL_BY), Owner (Snowflake role that owns table), Definition Altered Date, Table Size | | View | Name, Comments, Schema, External URL (Snowsight), Definition Altered Date, Last Modified By (Snowflake LAST_DDL_BY), Is Iceberg, Is dynamic, Is temporary, Created Date, Last Modified Date, Owner (Snowflake role that owns table), SQL definition | | Materialized View | Name, Comments, Schema, External URL (Snowsight), Definition Altered Date, Last Modified By (Snowflake LAST_DDL_BY), Is Iceberg, Is dynamic, Is temporary, Created Date, Last Modified Date, Owner (Snowflake role that owns table) | | Schema | Identifier, Name Extended metadata: Comments, Created date, Updated | | Database | Type, Name, Identifier, Server, Port, Environment, JDBC URL Extended metadata: Comments | | User-defined function (this includes User-defined functions created in Snowpark) | Name Extended metadata: Function Definition, Comments, Created Date, Owner (Snowflake Role), Snowflake Function Type (Return Type), Function Signature, Function Language, Packages, Runtime version, Updated | | Stored Procedure (this includes Stored Procedures created in Snowpark) | Name Extended metadata: Function Definition, Owner (Snowflake Role), Comments, Return Type, Function Language, Packages, Created Date, Function signature, Snowflake Function Type, Runtime Version, Updated, Stored Procedure Type | [Table 1. Metadata harvested] {#snowflake-metadata-collector__table_wtx_nqh_phc} ## Relationships between objects {#snowflake-metadata-collector__section_qh1_l5h_phc} The harvested metadata includes catalog pages for the following data asset types. Each catalog page has a relationship to the other related data asset types. {#snowflake-metadata-collector__table_vzr_p5h_phc__entry__2} | Data asset page | Relationships | |-|-| | Snowflake Row access policies | Tables | | Snowflake Masking Policies | Columns, Tag value | | Table | Columns, Tag value, Data Metric Function that analyzes, Views, Tables, or Functions which the Table depends on | | Snowflake Tags | Tag value | | Columns | Table, Tag Value, System Tag Value | | View | Schema that contains Views, Columns that are part of Views, Data Metric Function that analyzes View, Views, Tables, or Functions which the View depends on | | Materialized View | Schema that contains Materialized Views, Columns that are part of Materialized Views | | Schema | Database that contains Schema, Table that is part of Schema, View that is part of Schema, Materialized View that is part of Schema, Streamlit app that is part of schema | | Streamlit App | Schema that contains Streamlit App | | Database | Schema contained in Database | | Data Metric Function | Table or View analyzed by this Snowflake Data Metric Function, Table, Views, Tables, or Functions which the Function depends on | [Table 2. Relationships between harvested data asset pages] {#snowflake-metadata-collector__table_vzr_p5h_phc} ## Lineage and dependencies for Snowflake {#snowflake-metadata-collector__section_gvd_sxm_phc} The following lineage information is collected by the Snowflake collector. Note that any lineage for SQL Statements defined via variable statements are not supported. Important things to note: * Any lineage for SQL Statements defined via variable statements are not supported. * The collector traces these relationships from a View's columns to ultimate source Table columns across SQL expressions and subqueries. {#snowflake-metadata-collector__ul_nd2_lj4_phc} {#snowflake-metadata-collector__table_dvy_vzm_phc__entry__2} | Object | Lineage available | |-|-| | Column in 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 | | User-defined function | A Function and: * Views referenced in Function * Tables referenced in Function * Functions referenced in Function A View and Function referencing View | | 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 by this stored procedure. Note: The following stored procedures are not supported: * Stored procedures with multitable inserts. However, multiple separate insert statements that insert into one table *are supported*. * Stored procedure with multiple SELECT and INSERT statements not separated by a semicolon delimiter. * Stored procedures used to create tables or any transient tables created during the execution scope of a stored procedure. | [Table 3. Object Lineage Availability] {#snowflake-metadata-collector__table_dvy_vzm_phc} Dependencies The Snowflake collector catalogs dependencies between tables, views, and functions using the Snowflake Account Usage view OBJECT_DEPENDENCIES. See the Snowflake documentation for more information about the OBJECT_DEPENDENCIES view. If you include the profiling and sampling specific parameters while running the collector, the following additional information is harvested for Columns. Note: The user/role must have read access to data to be able to harvest profiling information (column statistics). {#snowflake-metadata-collector__table_bvx_ddp_13c__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) | | Table | * Row Count * Sample Count (Target sample size) | [Table 4. Profiling and sampling specific information] {#snowflake-metadata-collector__table_bvx_ddp_13c} Following additional information is cataloged when you run the collector with the Collect Snowflake policy information and Collect Snowflake tag information options enabled. {#snowflake-metadata-collector__table_ovm_lvb_n3c__entry__2} | Object | Information cataloged | |-|-| | Columns | Snowflake masking policies | | Snowflake Tags | Name, Allowed Values, Comments | | Snowflake Tag Values | Name, Value | | Snowflake Masking Policies | Name, Comments , Date created, Snowflake tags, Owner, Type, Policy body, Schema, Database | | Snowflake Row access policies | Name, Comments , Date created, Snowflake tags, Owner, Type, Policy body, Schema, Database | [Table 5. Cataloged Snowflake tags and policies] {#snowflake-metadata-collector__table_ovm_lvb_n3c} Following additional information is cataloged when you run the collector with the Collect Snowflake table usage information and Table usage lookback days options enabled. {#snowflake-metadata-collector__table_ebb_3xb_n3c__entry__2} | Object | Information cataloged | |-|-| | Table | Query Count | [Table 6. Cataloged Snowflake table query counts] {#snowflake-metadata-collector__table_ebb_3xb_n3c} Following additional information about [data quality metrics](https://docs.snowflake.com/en/user-guide/data-quality-system-dmfs) is cataloged when you run the collector with the Collect data metric function information option enabled. {#snowflake-metadata-collector__table_yqd_rxb_n3c__entry__2} | Object | Information cataloged | |-|-| | Data Metric Function | * Identifier: Name of the function * Title: Name of the function * Description * Body Definition of the function | | Table | * Schedule: cron expressions * Data metric function observations: function name, column arguments, most recent metric time, value | [Table 7. Cataloged Snowflake Data Metric Functions] {#snowflake-metadata-collector__table_yqd_rxb_n3c} Following additional information is cataloged when you run the collector with theCollect Streamlit app information option enabled. {#snowflake-metadata-collector__table_u5h_vxb_n3c__entry__2} | Object | Information cataloged | |-|-| | Snowflake Streamlit App | * Identifier: App Name * Title: App Title * Description: App comments * Main file * Root location * Date Created * Owner | [Table 8. Cataloged Snowflake Streamlit Applications] {#snowflake-metadata-collector__table_u5h_vxb_n3c} * **[Prepare to run the Snowflake collector](https://www.servicenow.com/docs/BWT3zCjYul7JqR4m1V7Ghg)** Set up authentication and grant role permissions to enable Snowflake metadata collection. * **[Create a Snowflake metadata collector](https://www.servicenow.com/docs/HN09fB8bALwJQmIKK35d0w)** Create a collector to import metadata from Snowflake.