> For the complete documentation index, see [llms.txt](https://docs.euno.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.euno.ai/sources/data-warehouses/sql-server-integration/sql-server-integration-discovered-resources.md). # SQL Server Integration Discovered Resources The Euno SQL Server integration discovers and updates the following resource families: * SQL Server instances * SQL Server databases * SQL Server schemas * SQL Server tables, views, and indexed views * SQL Server table and view columns * SQL Server linked servers * Usage and workload lineage from Query Store when enabled By default, URI host identity preserves the configured hostname and any SQL Server named instance. For example, `SQL01.corp.example.com\DW` becomes `sql01.corp.example.com_sqlserver_instance_dw` in URI paths. Configure **Override SQL Server Hostname for URIs** when you want a different externally canonical URI host, such as `sql01`. ## Resource hierarchy ``` SQL Server Instance └── Database └── Schema ├── Table / View / Indexed View │ └── Column └── ... SQL Server Instance └── Linked Server ``` ## Ingested resources ### SQL Server instance (`sqlserver_instance`) Represents the SQL Server or Azure SQL instance configured in the source. | Property | Description | | --------------------- | --------------------------------------------------------------------- | | `name` | Instance name. Defaults to the configured hostname unless overridden. | | `type` | Always `sqlserver_instance`. | | `subtype` | Always `sqlserver_instance`. | | `container_type` | SQL Server container classification. | | `database_technology` | Always `sqlserver`. | **URI pattern** ``` platform.sqlserver. ``` ### SQL Server database (`database`) Represents a user database within the SQL Server instance. | Property | Description | | --------------------- | ---------------------------------- | | `name` | Database name. | | `type` | Always `database`. | | `subtype` | Always `database`. | | `container_type` | Database container classification. | | `parent_container` | Parent SQL Server instance URI. | | `database_technology` | Always `sqlserver`. | **URI pattern** ``` mssql.. ``` ### SQL Server schema (`database_schema`) Represents a schema within a SQL Server database. | Property | Description | | --------------------- | -------------------------------- | | `name` | Schema name. | | `type` | Always `database_schema`. | | `subtype` | Always `database_schema`. | | `container_type` | Schema container classification. | | `parent_container` | Parent database URI. | | `database_database` | Database name. | | `database_technology` | Always `sqlserver`. | **URI pattern** ``` mssql... ``` ### SQL Server table (`table`, subtype `base_table`) Represents a SQL Server base table. | Property | Description | | ----------------------------------- | -------------------------------------------------------------------- | | `name` | Table name. | | `type` | Always `table`. | | `subtype` | `base_table`. | | `description` | Table description from extended properties, when present. | | `parent_container` | Parent schema URI. | | `database_database` | Database name. | | `database_schema` | Schema name. | | `database_technology` | Always `sqlserver`. | | `platform_uri_prefix` | SQL Server URI prefix for the source. | | `row_count` | Table row count when size extraction is enabled and permitted. | | `volume` | Storage size in bytes when size extraction is enabled and permitted. | | `table_properties` | Structured table metadata, including materialization information. | | `table_schema` | Structured column list for observed columns. | | `table_dependencies` | Upstream table dependencies from catalog and SQL parsing inputs. | | `sqlserver_definition_dependencies` | SQL Server catalog definition dependencies. | | `foreign_key_dependencies` | Foreign-key target table URIs. | | `native_raw_object` | Raw SQL Server metadata snapshot. | **URI pattern** ``` mssql.... ``` Example: `mssql.sql01.salesdb.dbo.customers` ### SQL Server view (`table`, subtype `view`) Represents a SQL Server view. View resources use the same URI pattern and common table properties as base tables. Euno also stores view SQL as code metadata and uses catalog dependencies and SQL parsing to populate table lineage. **URI pattern** ``` mssql.... ``` ### SQL Server indexed view (`table`, subtype `materialized_view`) Represents a SQL Server indexed view. Euno models indexed views as materialized views. Indexed view resources use the same URI pattern and common table properties as tables and views. **URI pattern** ``` mssql.... ``` ### SQL Server column (`column`) Represents a column within a SQL Server table, view, or indexed view. | Property | Description | | ------------------------------------------- | ---------------------------------------------------------- | | `name` | Column name. | | `type` | Always `column`. | | `subtype` | Always `column`. | | `description` | Column description from extended properties, when present. | | `parent_container` | Parent table/view URI. | | `database_database` | Database name. | | `database_schema` | Schema name. | | `database_technology` | Always `sqlserver`. | | `native_data_type` | Native SQL Server data type. | | `normalized_data_type` | Euno-normalized data type. | | `is_primary_key` | Whether the column participates in a primary key. | | `is_computed` | Whether the column is computed. | | `computed_definition` | Computed-column SQL expression, when available. | | `is_persisted` | Whether a computed column is persisted. | | `qualified_code_based_columns_dependencies` | Upstream column URIs from SQL parsing. | | `foreign_key_dependencies` | Foreign-key target column URIs. | **URI pattern** ``` mssql.....column. ``` Example: `mssql.sql01.salesdb.dbo.customers.column.customerid` ### SQL Server linked server (`sqlserver_linked_server`) Represents a linked server configured on the SQL Server instance. | Property | Description | | --------------------- | ---------------------------------------- | | `name` | Linked server name. | | `type` | Always `sqlserver_linked_server`. | | `subtype` | Always `sqlserver_linked_server`. | | `container_type` | Linked-server container classification. | | `parent_container` | Parent SQL Server instance URI. | | `database_technology` | Always `sqlserver`. | | `product` | Linked server product metadata. | | `provider` | Linked server provider metadata. | | `data_source` | Linked server data source. | | `default_catalog` | Linked server default catalog, when set. | **URI pattern** ``` mssql..linked_server. ``` Example: `mssql.sql01.linked_server.erp_link` ## Query Store usage and lineage When Query Store is enabled and readable, Euno can enrich table resources with workload metadata: | Property | Description | | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | `query_count_by_window_days` | Number of Query Store statements that read the table, as a dict keyed by the lookback window in days (e.g. `{"30": 1234}`). | | `write_count_by_window_days` | Number of Query Store statements that write to the table, as a dict keyed by the lookback window in days (e.g. `{"30": 1234}`). | | `last_accessed_at` | Last observed read access time. | | `last_written_at` | Last observed write time. | | `popular_queries` | Representative popular Query Store statements for the table. | | `query_store_upstream` | Upstream table URIs inferred from Query Store workload lineage. | | `query_store_lineage_execution_count` | Number of Query Store executions supporting an inferred workload lineage edge. | Each usage count is keyed by the effective lookback window in days (stringified). Because each crawl overwrites the dict wholesale, only the current window is present and stale windows are cleared automatically. Query Store lineage also contributes to the canonical `table_dependencies` relationship. Query Store does not provide per-user attribution for this integration. The resource sidepane's **Usage** tab displays these read and write counts using the effective Query Store window, together with the latest access timestamps and the representative popular-query sample. ## Exact resource model The integration emits the following resource types and subtypes: ``` sqlserver_instance database database_schema table subtype base_table table subtype view table subtype materialized_view column sqlserver_linked_server ``` ## URI examples ``` mssql.sql01.salesdb.dbo.customers mssql.sql01.salesdb.dbo.customers.column.customerid mssql.sql01.linked_server.erp_link ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.euno.ai/sources/data-warehouses/sql-server-integration/sql-server-integration-discovered-resources.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.