> 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/release8.2/connectors/connector-repositories/rdbms/mysql/mysql-lineage.md).

# MySQL - Lineage

This article outlines the lineage coverage, configuration settings, metadata handling, supported scenarios, component behaviors, process flow, and known gaps for lineage extraction in MySQL. The lineage process analyzes SQL statements from datasets, views, and query logs to generate table-level and column-level lineage. It helps improve data visibility and impact analysis by tracking data movement across tables, views, and SQL-based transformations within MySQL environments.

## Lineage Configuration Requirements

Accurate lineage extraction depends on specific configuration settings and metadata availability. 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="250">Configuration</th><th>Required Detail</th></tr></thead><tbody><tr><td>MySQL Connection</td><td>MySQL connection must be configured and successfully crawled</td></tr><tr><td>Dataset SQL</td><td>Datasets must contain valid SQL statements</td></tr><tr><td>Schema Metadata Availability</td><td>Required schemas and tables must be available in metadata</td></tr><tr><td>Query Log Ingestion</td><td>Query log ingestion can be enabled to support runtime lineage extraction</td></tr><tr><td>Lineage Processing Limits</td><td>Recommended lineage processing limit settings should be configured</td></tr><tr><td>Query Cleanup</td><td>Query cleanup is recommended to improve SQL parsing success</td></tr></tbody></table>

{% hint style="warning" %}
Missing metadata, invalid SQL statements, or unavailable schema information may prevent lineage generation or result in incomplete lineage paths.
{% endhint %}

## Lineage Components

| Component                     | Availability |
| ----------------------------- | :----------: |
| Tables                        |       ✅      |
| Views                         |       ✅      |
| Columns                       |       ✅      |
| SQL Queries (Static SQL)      |       ✅      |
| Query Logs                    |      ⚠️      |
| Stored Procedures / Functions |      ⚠️      |
| Triggers                      |      ⚠️      |
| Temporary Objects             |      ⚠️      |
| Cross-Schema References       |      ⚠️      |
| Dynamic SQL                   |       ❌      |

{% 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

| Transformation Type   | Supported |
| --------------------- | :-------: |
| Direct Column Mapping |     ✅     |
| Alias Mapping         |     ✅     |
| Expressions           |     ⚠️    |
| Aggregations          |     ⚠️    |
| Derived Columns       |     ⚠️    |
| Temporary Columns     |     ⚠️    |

{% 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 MySQL SQL workloads and metadata-driven transformations. These use cases represent scenarios where lineage extraction functions as expected.

### Supported Lineage Scenarios

<table><thead><tr><th width="261">Supported</th><th>Details</th></tr></thead><tbody><tr><td>View to Source Table Lineage</td><td>Lineage extraction from views to the underlying source tables</td></tr><tr><td>Table to Table Lineage</td><td>Tracking lineage between source and target tables</td></tr><tr><td>Direct Column Mapping</td><td>Source-to-target column mapping for direct assignments</td></tr><tr><td>Alias Mapping</td><td>Lineage for renamed columns and aliases</td></tr><tr><td>Simple Expression Lineage</td><td>Column lineage for basic SQL expressions</td></tr><tr><td>Cross-Schema Lineage</td><td>Lineage across schemas within the same MySQL instance</td></tr><tr><td>Static SQL-Based Transformations</td><td>Lineage generated from static SQL-based ELT processes</td></tr><tr><td>Query Log Lineage</td><td>Lineage extraction from supported query log information</td></tr></tbody></table>

{% hint style="info" %}
Lineage extraction is based on SQL statements available in datasets, views, and supported query log sources.
{% endhint %}

## Partial or Limited Coverage

Certain scenarios provide only partial lineage coverage due to SQL complexity, metadata limitations, or processing constraints.

### Scenarios

<table><thead><tr><th width="287">Scenario</th><th>Limitation Description</th></tr></thead><tbody><tr><td>Stored Procedures and Functions</td><td>Coverage is limited to static SQL portions that can be analyzed</td></tr><tr><td>Triggers</td><td>Only supported where static SQL logic can be extracted</td></tr><tr><td>Complex SQL Queries</td><td>Nested queries, multiple CTEs, and complex query structures may not be fully resolved</td></tr><tr><td>UNION Operations</td><td>Lineage generation may be incomplete for UNION-based queries</td></tr><tr><td>Aggregations</td><td>Partial column-level lineage for aggregation functions</td></tr><tr><td>Derived Columns</td><td>Complex derivation logic may not be fully represented</td></tr><tr><td>Temporary Tables and Objects</td><td>Temporary object lineage may be incomplete</td></tr><tr><td>Cross-Connection or Federated Queries</td><td>Limited support for lineage across external or federated sources</td></tr><tr><td>Non-ASCII Queries</td><td>SQL parsing may be limited for non-ASCII query content</td></tr></tbody></table>

{% hint style="warning" %}
Complex SQL patterns and temporary processing structures may result in incomplete column-level lineage even when lineage extraction succeeds.
{% endhint %}

## Unsupported Scenarios

The connector does not support lineage extraction for certain SQL execution patterns and procedural logic due to limitations in metadata availability and query resolution.

### Unsupported Lineage

| Not Supported                    | Description                                                                      |
| -------------------------------- | -------------------------------------------------------------------------------- |
| Dynamic SQL                      | Runtime-generated SQL statements                                                 |
| Procedural Logic                 | Complex logic involving loops, conditions, and cursors                           |
| Application-Level Embedded SQL   | SQL executed within applications that are not captured as datasets or query logs |
| Runtime Query Generation         | Queries constructed dynamically during execution                                 |
| Non-Captured External Processing | Transformations performed outside available metadata and query sources           |

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

## Current Functional Status

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

<table><thead><tr><th width="210">Status Area</th><th>Details</th></tr></thead><tbody><tr><td>Overall Coverage</td><td>Partial coverage across MySQL SQL workloads</td></tr><tr><td>Lineage Depth</td><td>Reliable table-level lineage with basic column-level lineage support</td></tr><tr><td>Supported Inputs</td><td>Tables, views, datasets, static SQL queries, and query logs</td></tr><tr><td>Functional Scope</td><td>Lineage extraction for standard SQL-based transformations and object relationships</td></tr><tr><td>Limitation Areas</td><td>Dynamic SQL, procedural logic, complex queries, aggregations, derived columns, and federated processing</td></tr><tr><td>Resulting Output</td><td>Strong table-level lineage with column-level lineage available for supported SQL patterns</td></tr></tbody></table>

{% hint style="warning" %}
Coverage remains partial because dynamic SQL, procedural logic, complex transformations, and certain query structures cannot be fully resolved. Manual validation or lineage adjustments may be required for advanced MySQL workloads.
{% 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, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/release8.2/connectors/connector-repositories/rdbms/mysql/mysql-lineage.md?ask=<question>&goal=<endgoal>
```

`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.