> 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.3/connectors/introduction-to-connectors/connector-features/crawling.md).

# Crawling

Crawling is the process of collecting metadata from a connected data source. This metadata includes details such as databases, tables, columns, reports, files, code, APIs, and their attributes.

Data sources can include systems like databases, data lakes, or reporting tools.
 After crawling is complete, the collected metadata will be available in the Data Catalog.

**Example**:\
For a SQL Server data source, crawling retrieves information such as Table Name, Column Name, Data Type, Data Type Size, Title, and Description.\
The screenshot below shows metadata from a sample database table in a SQL Server Data Source.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXd_U47Mu1SOJqjRl5KDfJjYDZQugLVSKCeK0126P4Mc51Y_Y8rh3FzEiCOIHpePcx_OPUpaei19Tuy9qfDOL8SQVNG-co_9gOUg0tMUgxaI3SPdCOzivbW-6PNCHwgGX2Ibph9Q?key=kU5fqtI4eAzquyCyuBsp-g" alt=""><figcaption></figcaption></figure>

The system connects to the SQL Server, crawls the table, and fetches the metadata as shown.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfRrL4pSL7DgUzm7ulit5KunyZI6WTBcr_9N3hbrj5K67tiC-V69PB1DIGNMxNMRcR5aZPWHFAJPUw2cuGuVnLQ7YUs3_3pR50e-cEUflcWBZ4OL1WRF4ltNtasm434PMXnvEiv6g?key=kU5fqtI4eAzquyCyuBsp-g" alt=""><figcaption></figcaption></figure>

***

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/release8.3/connectors/introduction-to-connectors/connector-features/crawling.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.