> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/connectors/connector-repositories/rdbms/microsoft-sql-server/microsoft-sql-server-lineage.md).

# Microsoft SQL Server - Lineage

This article outlines the lineage coverage, configuration requirements, metadata handling, supported scenarios, component behaviors, transformation coverage, and known limitations for lineage extraction in Microsoft SQL Server. The lineage process provides end-to-end visibility into data movement across SQL Server datasets and transformations. It supports table-level and column-level lineage for standard SQL workloads, helping organizations track data dependencies and perform impact analysis efficiently.

## Lineage Configuration Requirements

Accurate lineage extraction depends on SQL Server connectivity, metadata availability, and access to dependent objects. These requirements must be properly configured and available to ensure successful lineage generation and source-target resolution.

### Configuration Requirements Table

<table><thead><tr><th width="271">Configuration</th><th>Required Detail</th></tr></thead><tbody><tr><td>SQL Server Connection</td><td>Secure access to Microsoft SQL Server must be configured</td></tr><tr><td>Metadata Access</td><td>Permissions to read database objects and metadata are required</td></tr><tr><td>Dependent Object Availability</td><td>All dependent objects should be available for lineage processing</td></tr><tr><td>Optional Lineage Configurations</td><td>Optional configurations can be enabled to improve the handling of complex lineage scenarios</td></tr></tbody></table>

{% hint style="info" %}
Missing permissions, inaccessible database objects, or unavailable metadata may result in incomplete lineage generation.
{% endhint %}

## Lineage Components

| Component                 | Availability |
| ------------------------- | :----------: |
| Tables                    |       ✅      |
| Views                     |       ✅      |
| Stored Procedures         |       ✅      |
| Triggers                  |       ✅      |
| Functions                 |      ⚠️      |
| Temp Tables               |      ⚠️      |
| Synonyms                  |      ⚠️      |
| Linked Server (OPENQUERY) |      ⚠️      |
| Nested Procedures         |      ⚠️      |
| Cross-Connection Objects  |      ⚠️      |
| Dynamic SQL               |       ❌      |
| Encrypted Objects         |       ❌      |

{% hint style="info" %}
The ⚠️ icon indicates partially supported functionality with limited lineage coverage in applicable scenarios.
{% endhint %}

## Column Creation Support

This section outlines lineage support for column creation and transformation scenarios.

### Column Creation from Lineage

| Feature                       | Supported |
| ----------------------------- | :-------: |
| Direct Column Mapping         |     ✅     |
| Derived Columns               |     ✅     |
| Aggregations (SUM, MAX, etc.) |     ⚠️    |
| Expressions / CASE Statements |     ⚠️    |
| Aliases                       |     ⚠️    |
| SELECT \* Expansion           |     ⚠️    |
| Dynamic Column Generation     |     ❌     |

{% hint style="info" %}
The ⚠️ icon indicates partially supported functionality with limited lineage coverage in applicable scenarios.
{% endhint %}

## Supported Use Cases

The connector supports lineage extraction across standard SQL Server workloads and object relationships. These use cases represent scenarios where lineage extraction functions as expected.

### Supported Lineage Scenarios

<table><thead><tr><th width="343">Supported</th><th>Details</th></tr></thead><tbody><tr><td>View-Based Transformations</td><td>Lineage extraction across views and underlying source objects</td></tr><tr><td>Stored Procedure Workflows (Static SQL)</td><td>Lineage extraction from stored procedures containing static SQL</td></tr><tr><td>Query Log Lineage</td><td>Lineage generated from available query execution information</td></tr><tr><td>Cross-Schema Lineage</td><td>Lineage across schemas within the same SQL Server environment</td></tr></tbody></table>

{% hint style="info" %}
Lineage extraction is based on accessible SQL definitions, metadata, and supported SQL Server objects available through the configured connection.
{% endhint %}

## Partial or Limited Coverage

Certain scenarios provide only partial lineage coverage due to query complexity, object resolution limitations, or metadata dependencies.

### Scenarios

<table><thead><tr><th width="252">Scenario</th><th>Limitation Description</th></tr></thead><tbody><tr><td>Functions (UDFs)</td><td>Partial lineage coverage for user-defined functions</td></tr><tr><td>Temp Tables (#)</td><td>Lineage may be incomplete for temporary tables</td></tr><tr><td>Linked Server (OPENQUERY)</td><td>Limited SQL parsing and object resolution</td></tr><tr><td>Nested Procedures</td><td>Partial resolution of procedure dependencies</td></tr><tr><td>Cross-Connection Lineage</td><td>Coverage depends on configuration and metadata availability</td></tr><tr><td>Complex SQL Logic</td><td>Reduced lineage accuracy for complex SQL transformations</td></tr></tbody></table>

{% hint style="warning" %}
Advanced SQL logic and cross-system dependencies may result in incomplete lineage paths or reduced column-level lineage accuracy.
{% endhint %}

## Unsupported Scenarios

The connector does not support lineage extraction for certain runtime-generated, encrypted, or external processing patterns due to limitations in metadata availability and SQL accessibility.

### Unsupported Lineage

<table><thead><tr><th width="245">Not Supported</th><th width="273">Impact</th><th width="352">Workaround</th></tr></thead><tbody><tr><td>Dynamic SQL (EXEC, runtime queries)</td><td>No lineage generated</td><td>Use query logs or manual lineage</td></tr><tr><td>Encrypted Objects</td><td>SQL definitions cannot be read</td><td>Remove encryption or document manually</td></tr><tr><td>Runtime-generated Tables/Columns</td><td>No lineage generated</td><td>Use static SQL alternatives</td></tr><tr><td>Unsupported SQL Syntax</td><td>Parsing failure</td><td>Simplify SQL or use dataset correction</td></tr><tr><td>External/Non-SQL Logic (CLR, scripts)</td><td>Not captured in lineage</td><td>Document separately</td></tr></tbody></table>

{% hint style="info" %}
Unsupported scenarios will not produce lineage and may appear disconnected in lineage visualization.
{% endhint %}

## Current Functional Status

This section outlines the present state of lineage coverage supported by the Microsoft SQL Server connector based on the available capabilities and limitations.

<table><thead><tr><th width="215">Status Area</th><th>Details</th></tr></thead><tbody><tr><td>Overall Coverage</td><td>Strong coverage across standard SQL Server workloads</td></tr><tr><td>Lineage Depth</td><td>Reliable table-level and column-level lineage</td></tr><tr><td>Supported Inputs</td><td>Tables, views, stored procedures, triggers, query logs, and supported database objects</td></tr><tr><td>Functional Scope</td><td>Lineage extraction for standard SQL transformations and object dependencies</td></tr><tr><td>Limitation Areas</td><td>Functions, temp tables, linked servers, nested procedures, cross-connection lineage, and complex SQL logic</td></tr><tr><td>Resulting Output</td><td>Reliable lineage for most SQL Server workloads with partial coverage for advanced scenarios</td></tr></tbody></table>

{% hint style="warning" %}
The Microsoft SQL Server connector is production-ready with strong support for standard SQL Server workloads, including reliable table-level and column-level lineage. Advanced scenarios such as complex SQL logic, cross-connection lineage, linked server queries, and user-defined functions may have partial coverage depending on implementation complexity and metadata availability.
{% endhint %}

***

&#x20;Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA


---

# 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:

```
GET https://docs.ovaledge.com/connectors/connector-repositories/rdbms/microsoft-sql-server/microsoft-sql-server-lineage.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.