--- 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 --- # Microsoft SQL Server metadata collector # Microsoft SQL Server metadata collector {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 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 Microsoft SQL Server metadata collector The Microsoft SQL Server metadata collector provides read-only access to metadata from Microsoft SQL Server accounts, including self-hosted instances and managed instances on platforms like AWS RDS or Azure SQL. It harvests a wide range of metadata from databases---such as tables, columns, views, stored procedures, functions, and Agent jobs---and makes this information searchable and discoverable within the ServiceNow data catalog. Show full answer Show less ## Cataloged Metadata The collector catalogs extensive metadata details across various SQL Server objects, including: * **Agent Jobs**: Detailed job properties, notifications, job steps, and execution history. * **Tables and Columns**: Names, types, keys, defaults, sizes, indexes, and extended properties. * **Views and Materialized Views**: Definitions, descriptions, schemas, and creation/modification metadata. * **Functions and Stored Procedures**: Names, descriptions, types, definitions, and versioning for overloaded procedures. * **Publications, Articles, and Subscriptions**: Replication settings, synchronization, filters, commands, and statuses. * **Synonyms** and other database objects. When profiling and sampling parameters are enabled, additional statistical data about columns is collected, such as average and maximum lengths, value distributions, distinct counts, and sample values. ## Relationships and Lineage The collector identifies and catalogs relationships between data assets, such as which job steps belong to agent jobs, which columns belong to views or schemas, and dependencies among tables, views, and stored procedures. It also harvests lineage information at the column level for views and stored procedures, showing sources for data sourcing, sorting, filtering, aggregation, and downstream table updates. **Limitations:** Lineage is only collected within the specified server and databases; cross-server lineage is not supported. Multitable inserts are not supported, and multiple SQL statements must be semicolon-separated for proper parsing. ## Preparation and Usage Before running the collector, configure appropriate authentication and permissions on the Microsoft SQL Server instance. Then, create and configure the metadata collector within ServiceNow to import metadata. This collector enables ServiceNow customers to effectively catalog and explore detailed SQL Server metadata, supporting data governance, impact analysis, and improved data discovery within their enterprise. Provides read-only access to metadata from a Microsoft SQL Server account. The collector harvests metadata from Microsoft SQL Server databases, including tables, columns, views, schemas, stored procedures, functions, and Agent jobs, making them searchable and discoverable in the data catalog. Supports both self-hosted Microsoft SQL Server instances and managed instances, such as those hosted on AWS RDS or Azure SQL. ## Metadata cataloged {#microsoft-sql-server-metadata-collector__section_xmz_pbp_13c} The 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. {#microsoft-sql-server-metadata-collector__table_wxx_2cp_13c__entry__2} | Object | Information cataloged | |-|-| | Agent Job | Name, Description, Version, Enabled, Category, Server Name, Created Date, Last Modified Date, Owner, Starting Job Step, Email Notification Level, Page Notification Level, Network Notification Level, Event Log Notification Level, Delete Notification Level, Email Notification Sent To, Page Notification Sent To, Network Notification Sent To | | Agent Job Step | Name, Command, Subsystem, Flag, Additional Parameters, Server, Database, Database Username, Proxy ID, Output File, OS Run Priority, Retry Attempts, Retry Interval, Last Run Outcome, Last Run Duration, Last Run Date, Last Run Time, On Success Action, On Success Go To Step, On Failure Action, On Failure Go To Step | | Columns | Name, JDBC type, Column Type, Is Nullable, Default Value, Key type (Primary, foreign), Column size, Column index Extended property: Description | | Table | Name, Description, Primary key, Schema Extended metadata: Created date, Modified date | | Table Index | Index Cardinality, Column name, Index Type, Index Name, is non Unique, Ordinal Position, Pages, Sort Sequence | | Views | Name, Description, SQL definition | | Materialized View | Name, description | | Schema | Identifier, Name Extended metadata: Created date, Modified date | | Database | Type, Name, Identifier, Server, Port, Environment, JDBC URL | | Functions | Name, Description, Function Type | | Stored Procedures | Name, Description, Stored Procedure Type Extended metadata: Definition, Created, Last modified | | Publication | Name, Description, Status, Publication Type, Allow Push, Allow Pull, Allow Anonymous, Allow Subscription Copy, Retention, Enabled for Internet, Snapshot in Default Folder, Alternate Snapshot Folder, Pre Snapshot Script, Post Snapshot Script, Compress Snapshot, FTP Address, FTP Port, FTP Subdirectory, FTP Login, Active Directory Guid, Centralized Conflicts, Decentralized Conflicts, Conflict Retention, Backward Compatibility, Replicate DDL, Publication Sync Method, Immediate Sync, Immediate Sync Ready, Allow Queued Transaction, Allow Sync Transcation, Allow DTS, Options, Autogen Sync Procedure, Allow Initialize From Backup, Has Conflict Policy, Independent Agent, Is Filtered, Snapshot Status, Max Concurrent Merge, Allow Subscriber Initiated Snapshot, Allow Web Synchronization, Allow Sync To Alternate, Web SynchronizationUrl, Allow Partition Realignment, Generation Leveling Threshold, Automatic Reinitialization Policy | | Article | Name, Description, Destination Object, Destination Owner, Source Object, Source Owner, Filter Clause, Creation Script, Delete Command, Insert Command, Update Command, Status, Type, Precreation command, Executes Trigger On Snapshot | | Subscription | Description, Type, Sync Type, Status Server, Database, Queued Reinitialization, Login Name, Update Mode, Loopback Detection Send Back, No Sync Type, Subscriber Type, Datasource Type, Priority, Attempted Validate, Last Validated, Last Sync Date, Last Sync Status, Last Makegeneration Datetime, Replica Version, Cleanedup Unsent Changes | | Synonym | Name | [Table 1. Cataloged metadata] {#microsoft-sql-server-metadata-collector__table_wxx_2cp_13c} Note: All versions of overloaded functions and stored procedures are cataloged. Each version has its own title in the catalog but a distinct identifier. When profiling and sampling parameters are enabled, the following additional column information is cataloged: {#microsoft-sql-server-metadata-collector__table_h3b_52f_b3c__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 2. Profiling and sampling information] {#microsoft-sql-server-metadata-collector__table_h3b_52f_b3c} ## Relationship between objects {#microsoft-sql-server-metadata-collector__section_a3f_qbp_13c} Catalog pages show relationships between the following data asset types: {#microsoft-sql-server-metadata-collector__table_flr_x2f_b3c__entry__2} | Data asset page | Relationship | |-|-| | Agent Job | Agent Job contains Job Step | | Job Step | Job Step command is executed in Database | | Table | Columns, Table Indexes, Schema | | View | Schema that contains Views, Columns that are part of Views | | Materialized View | Schema that contains Materialized Views, Columns that are part of Materialized Views | | Columns | Table | | Schema | Database that contains Schema, Table that is part of Schema, View that is part of Schema, Materialized View that is part of Schema, Synonym | | Database | Schema contained in Database | | Publication | Contains Article, Has Parent Publication, Published by Publisher Database | | Article | Refers Table | | Subscription | Subscribes to Publication, Delivered To Subscriber Database, Delivery Executed By Distributor Database, Supplies Data to Table | [Table 3. Relationships between cataloged objects] {#microsoft-sql-server-metadata-collector__table_flr_x2f_b3c} ## Lineage and dependencies for Microsoft SQL Server {#microsoft-sql-server-metadata-collector__section_p5j_qbp_13c} The following lineage information is collected by the Microsoft SQL Server collector. This lineage information is available only for the target server and databases specified while running the collector. Harvesting lineage from referenced objects located in another server is not supported. {#microsoft-sql-server-metadata-collector__table_wdy_hff_b3c__entry__2} | Object | Lineage available | |-|-| | View | Column-level lineage showing source columns for: * Data sourcing * Sorting (ORDER BY) * Filtering (WHERE/HAVING) * Aggregation (GROUP BY) | | Stored Procedure | Column-level lineage showing source columns for data sourcing, sorting, filtering, and aggregation. Table-level lineage showing downstream tables updated by the procedure. | [Table 4. Lineage availability by object] {#microsoft-sql-server-metadata-collector__table_wdy_hff_b3c} Note: The collector parses SQL to harvest lineage metadata. For Views, if SQL parsing fails, the collector uses the `dm_sql_referencing_entities` system function when available. For Stored Procedures, the collector parses INSERT, UPDATE, and SELECT statements and additionally uses the `dm_sql_referencing_entities`system function when available. Limitations:Multitable inserts are not supported.Multiple SELECT and INSERT statements must be separated by semicolon delimiters. The collector catalogs dependencies between tables, views, and stored procedures using `sys.sql_expression_dependencies`. Dependencies are created when one entity appears by name in a persisted SQL expression of another entity. See the [Microsoft SQL Server dependencies documentation](https://learn.microsoft.com/en-us/sql/relational-databases/system-catalog-views/sys-sql-expression-dependencies-transact-sql?view=sql-server-ver16) for details. * **[Prepare to run the Microsoft SQL Server collector](https://www.servicenow.com/docs/5WLlkWlC3ROMOjetFA~jJg#prepare-to-run-microsoft-sql-server-collector)** Configure authentication and permissions before running the collector. * **[Create a Microsoft SQL Server metadata collector](https://www.servicenow.com/docs/WPA3Aro4_H2bwjBArYHFTA)** Create a collector to import metadata from Microsoft SQL Server.