> 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/release7.2/connectors/introduction-to-connectors/connector-features/lineage.md).

# Lineage

Data lineage represents the complete lifecycle of data as it moves from source to destination. It involves the collection of metadata that describes how data is created, transformed, and utilized across systems. This capability ensures transparency, trust, and governance in data environments.

### Manual Lineage

Manual lineage enables the construction of data flow mappings through direct user input. This approach is suitable for specific or custom scenarios that require manual configuration.

Steps to Establish Manual Lineage:

* Navigate to a specific table or go to the lineage maintenance section.
* Add the source and destination tables based on the requirements.

### Auto Lineage

Auto lineage traces data flow automatically using system logic. It reduces manual work and improves accuracy.

**Steps to Establish Auto Lineage:**

* **Connection Configuration**: Select the auto lineage option during connector setup, based on the license type.
* **Metadata Crawling**: Execute crawling for procedures, triggers, functions, source code, and views to collect required metadata.
* The lineage build process begins from the connectors page by selecting the 9-dots option and choosing "**Build Auto Lineage**." This opens the auto lineage page, where lineage can be built using five different methods.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeeDrQQd_gvb9Z0H2VYjykkqZW65Sw6N5Cb4SVxm3JOVdUgD3iDhid-Zxa50YH4SXR-u4pCvuGu7W0UnoWO-ZZaB8eV5t7jgtEPVRZ5N6v_wlFIDcW4TyR9pWIrhtqh8S_Kb04nrw?key=kU5fqtI4eAzquyCyuBsp-g" alt=""><figcaption></figcaption></figure>

[List of Auto Lineage supported Connectors](/release7.2/connectors/introduction-to-connectors/connector-features/lineage/auto-lineage-supported-connectors.md)

***

Copyright © 2025, 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ovaledge.com/release7.2/connectors/introduction-to-connectors/connector-features/lineage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.