> 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/introduction-to-connectors/configuration-and-management/crawl-and-profile.md).
# Crawl & Profile
When the connection is successfully validated and saved, click the "Crawl/Profile" button at the top right of the connector page to initiate the Crawl/Profile. The Crawl/Profile options vary from one connector type to another.
{% hint style="info" %}
Only the Integration Admin can perform this operation.
{% endhint %}
## RDBMS Connector
### **Schema List**
The system displays all available schemas from the connected database. Select the desired schema to initiate the crawl or profile process.
When multiple schemas exist, click the See More button at the bottom right to view the complete list.
### **Action**
The "Action" section contains various action items that can be executed on the selected schema.
#### **Crawl**
Crawling is the process of gathering metadata from data sources. The connectors can be scheduled to crawl databases regularly to keep metadata up-to-date.
#### **Profile**
Profiling collects statistics and data summaries from crawled sources.
{% hint style="info" %}
Profiling is only available for databases and files that have already been crawled or cataloged.
{% endhint %}
{% hint style="info" %}
Full Profiling jobs may use batch processing when enabled through the **enable.batch.profiling** system setting to improve execution performance and reduce bridge communication overhead.
{% endhint %}
#### **Crawl & Profile**
The "Crawl & Profile" option allows users to execute both crawl and profile operations in a single click.
#### **Profile Unprofiled**
The "Profile Unprofiled" option profiles unprofiled data within the connector. This option saves time by profiling only data that hasn't been profiled earlier.
#### Schedule
The "Schedule" option allows to automate the crawl and profile processes. There is an option to choose a timeframe ranging from a minute to a year.
### Report Connector
#### **Report Group List**
The system displays a list of all available report groups associated with the connected server. Select the desired report group to initiate the crawl process.
When multiple report groups are available, click the See More button at the bottom right to view the complete list.
#### **Action**
The "Action" section contains various action items that can be executed on the chosen report group.
**Crawl**
Crawling collects metadata from the source system. Connectors can be scheduled to run crawls regularly to keep the metadata up to date.
**Schedule**
The "Schedule" option allows to automate the crawl process. There is an option to choose a timeframe ranging from a minute to a year.
### File connector
Click the Crawl/Profile button to submit a job. This catalogs the first-level files and folders.
### API connector
* Click on the Crawl/Profile button.
* Choose the API Groups to crawl from the available options.
* From the selected group, choose one or more APIs from the list.
* Click on Crawl to start fetching metadata from the selected APIs.
#### Schedule
The "Schedule" option allows to automate the crawl process. There is an option to choose a timeframe ranging from a minute to a year.
### ETL connector
* Click on the Crawl/Profile button.
* Select the Schemas to crawl and profile.
* Choose the desired Schema from the list.
* Click on Crawl to begin fetching metadata from the selected schema.
**Schedule**
The "Schedule" option allows to automate the crawl process. There is an option to choose a timeframe ranging from a minute to a year.
***
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 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/introduction-to-connectors/configuration-and-management/crawl-and-profile.md?ask=&goal=
```
`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.