For the complete documentation index, see llms.txt. This page is also available as Markdown.

SQL Server Integration Discovered Resources

Overview

The Euno SQL Server integration discovers the databases, schemas, tables, views, columns, and linked servers of a SQL Server, Azure SQL, or Fabric SQL instance, together with usage and workload lineage from Query Store when enabled. It discovers the following resources:

  • SQL Server instance (sqlserver_instance)

  • SQL Server database (database)

  • SQL Server schema (database_schema)

  • SQL Server table (table, subtype base_table)

  • SQL Server view (table, subtype view)

  • SQL Server indexed view (table, subtype materialized_view)

  • SQL Server column (column)

  • SQL Server linked server (sqlserver_linked_server)

The instance URI uses the prefix platform.sqlserver.<hostname>. All other resources use the prefix mssql.<hostname>. Database, schema, table, and column names are lowercased in URIs.

By default, Euno normalizes the SQL Server hostname for URIs by keeping the first DNS label and stripping any \INSTANCE suffix. For example:

  • SQL01.corp.example.com\DW → URI host sql01

  • myserver.database.windows.net → URI host myserver

  • myhost-abc.database.fabric.microsoft.com → URI host myhost-abc

Configure Override SQL Server Hostname for URIs when you want a different canonical URI host. The override goes through the same first-label normalization as the configured hostname (for example, myserver.database.windows.net still becomes myserver in URIs).

Resource hierarchy

SQL Server instance (sqlserver_instance)

The SQL Server, Azure SQL, or Fabric SQL instance configured in the source.

Property
Type
Description

name

string

Instance name. Defaults to the configured hostname unless Override SQL Server Instance Name is set.

type

string

Always sqlserver_instance.

subtype

string

Always sqlserver_instance.

database_technology

string

Always mssql.

URI pattern

Example: platform.sqlserver.sql01

SQL Server database (database)

A user database within the SQL Server instance. The system databases master, tempdb, model, and msdb are not discovered.

Property
Type
Description

name

string

Database name.

type

string

Always database.

subtype

string

Always database.

database_technology

string

Always mssql.

URI pattern

Example: mssql.sql01.salesdb

SQL Server schema (database_schema)

A schema within a SQL Server database.

Property
Type
Description

name

string

Schema name.

type

string

Always database_schema.

subtype

string

Always database_schema.

database

string

Database name.

database_technology

string

Always mssql.

URI pattern

Example: mssql.sql01.salesdb.dbo

SQL Server table (table, subtype base_table)

A SQL Server base table.

Property
Type
Description

name

string

Table name.

type

string

Always table.

subtype

string

base_table.

description

string

Table description from extended properties, when present.

database

string

Database name.

database_schema

string

Schema name.

database_technology

string

Always mssql.

platform_uri_prefix

string

SQL Server URI prefix for the source (mssql.<hostname>).

row_count

number

Table row count when Extract Row Counts and Sizes is enabled and permitted.

volume

number

Storage size in bytes when Extract Row Counts and Sizes is enabled and permitted.

table_schema

object

Structured column list for observed columns.

total_read_queries_14d / _30d / _60d

number

Query Store read execution counts for each fully covered standard window. A property is unavailable when Query Store retention or the configured lookback is shorter than that window. Requires Extract Query Store Usage.

total_write_queries_14d / _30d / _60d

number

Query Store write execution counts for each fully covered standard window. A property is unavailable when Query Store retention or the configured lookback is shorter than that window. Requires Extract Query Store Usage.

query_count_by_window_days

object

Deprecated compatibility field containing read execution counts keyed by the effective Query Store lookback (for example, {"30": 1234}). Use total_read_queries_14d/30d/60d instead.

write_count_by_window_days

object

Deprecated compatibility field containing write execution counts keyed by the effective Query Store lookback (for example, {"30": 1234}). Use total_write_queries_14d/30d/60d instead.

last_accessed_at

timestamp

Last observed read access time, from Query Store.

last_written_at

timestamp

Last observed write time, from Query Store.

popular_queries

list

Representative popular Query Store statements for the table.

See Query Store usage and lineage for how the Query Store properties are measured.

URI pattern

Example: mssql.sql01.salesdb.dbo.customers

SQL Server view (table, subtype view)

A SQL Server view. Views also have the other common table properties listed for base tables (description, database, database_schema, database_technology, platform_uri_prefix, table_schema, and the Query Store properties), except row_count and volume. Euno also stores the view SQL as code metadata and uses it for lineage.

Property
Type
Description

name

string

View name.

type

string

Always table.

subtype

string

view.

table_properties

object

View definition SQL (T-SQL) and materialization information.

URI pattern

Example: mssql.sql01.salesdb.dbo.active_customers

SQL Server indexed view (table, subtype materialized_view)

A SQL Server indexed view. Euno models indexed views as materialized views. Indexed view resources use the same properties as views, and also receive row_count and volume when Extract Row Counts and Sizes is enabled.

URI pattern

Example: mssql.sql01.salesdb.dbo.daily_sales_summary

SQL Server column (column)

A column within a SQL Server table, view, or indexed view.

Property
Type
Description

name

string

Column name.

type

string

Always column.

subtype

string

Always column.

description

string

Column description from extended properties, when present.

database

string

Database name.

database_schema

string

Schema name.

database_technology

string

Always mssql.

native_data_type

string

Native SQL Server data type.

normalized_data_type

string

Euno-normalized data type.

URI pattern

Example: mssql.sql01.salesdb.dbo.customers.column.customerid

SQL Server linked server (sqlserver_linked_server)

A linked server configured on the SQL Server instance.

Property
Type
Description

name

string

Linked server name.

type

string

Always sqlserver_linked_server.

subtype

string

Always sqlserver_linked_server.

database_technology

string

Always mssql.

URI pattern

Example: mssql.sql01.linked_server.erp_link

Azure SQL Database and Microsoft Fabric SQL database do not support linked servers, so Euno skips linked-server discovery and continues with the database catalog.

Relationships

Each row is one relationship edge, written in the canonical direction for its family. Use the predicate in each heading to search for these relationships in EQL.

Containment (has parent / has child)

Source type
Relationship
Target type
Notes

database

has parent

sqlserver_instance

database_schema

has parent

database

table

has parent

database_schema

Includes views and indexed views.

column

has parent

table

sqlserver_linked_server

has parent

sqlserver_instance

Lineage (has upstream / has downstream)

Source type
Relationship
Target type
Notes

table

has upstream

table

Views and indexed views: tables and views referenced in the view definition, from catalog metadata (INFORMATION_SCHEMA.VIEW_TABLE_USAGE) and T-SQL parsing. Includes cross-database and linked-server references; see Cross-database and linked-server lineage.

table

has upstream

table

Tables referenced by the table's foreign keys. Self-referencing foreign keys do not create a table-level edge.

table

has upstream

table

Query Store workload lineage: a table written by a statement has upstream the tables that statement reads. Requires Extract Query Store Lineage.

Field-level lineage (has upstream_fields / has downstream_fields)

Source type
Relationship
Target type
Notes

column

has upstream_fields

column

View and indexed-view columns: parsed from the view definition.

column

has upstream_fields

column

Computed columns: columns referenced in the computed-column expression.

column

has upstream_fields

column

Foreign-key columns: the referenced primary or unique key column, including self-referencing foreign keys.

table

has upstream_fields

column

Views: columns used in SQL logic (for example JOIN conditions and WHERE filters) of the view definition, not only projected columns.

Cross-database and linked-server lineage

View-definition lineage resolves three-part names (database.schema.object) to tables in other databases on the same instance, and four-part names (server.database.schema.object) through the instance's linked servers:

  • When the linked server points to another SQL Server, the upstream table URI uses the remote server's data source as the host (normalized in the same way as the configured hostname), so the edge connects to resources discovered by a SQL Server source for that remote instance.

  • For other providers, or for linked servers Euno could not enumerate, the upstream table URI uses the linked server name as the host. The edge connects once that platform is integrated with a matching URI.

Query Store usage and lineage

When Query Store is enabled and readable, Euno can enrich table resources with workload metadata (total_read_queries_*, total_write_queries_*, last_accessed_at, last_written_at, popular_queries, and the deprecated query_count_by_window_days and write_count_by_window_days; see the SQL Server table section above).

Euno reads up to 60 days from Query Store by default and derives the standard windows from that one measurement. The effective lookback is clamped to Query Store retention. Only fully covered standard windows receive a number: for example, a 30-day effective lookback publishes 14- and 30-day totals and leaves the 60-day total unavailable. If individual Query Store statements cannot be attributed, the standard totals contain the resolved subset and may undercount; the run report keeps those parse failures visible. A capped workload leaves the standard totals unavailable. This preserves the distinction between measured history and history SQL Server did not provide. Query Store lineage contributes to has upstream on table resources when Extract Query Store Lineage is enabled. Query Store does not provide per-user attribution for this integration.

The resource sidepane's Usage tab displays these read and write counts with the standard 14-, 30-, and 60-day selector, together with the latest access timestamps and the representative popular-query sample. EQL can use the same cross-warehouse fields, for example total_read_queries_30d > 0.

See also SQL Server Usage Data.

Last updated