# Creating Data Profile

The *Data Profile* feature provides a complete data field statistic – basic and detailed – containing information such as the data type, minimum/maximum values, data count, error count, etc. The statistics are collected for each of the selected fields at the time the dataflow runs.

{% embed url="<https://youtu.be/9_Dj3Qxp27Y>" %}

## **Using Data Profile**

In this case, we will use data from a *Customers* [*Database Table Source*](https://documentation.astera.com/v/astera-data-stack-v8/dataflows/sources/database-table-source).

![](/files/0j9RQILtl7d9TjnifPXQ)

We want to collect statistics on these fields of data. For this purpose, we will use Astera's *Data Profile* feature.

1. To get the *Data Profile* object from the Toolbox, go to *Toolbox > Data Profiling > Data Profile*. If you are unable to see the Toolbox, go to *View > Toolbox* or press Ctrl + Alt + X.

![](/files/4C0UZH3uwwu3JrAUYTxz)

2. Drag and drop the *Data Profile* object onto the dataflow designer.

![](/files/MBLKLxDzAuANY3X8A2St)

You can see that the *Data* *Profile* object is empty right now. This is because we have not mapped any fields to it yet.

3. Auto-map the fields from the source object onto the profile object.

![](/files/QuVuaDuFtNrhO7cmPAS9)

{% hint style="info" %}
**Note:** A *Data Profile* object is designed to capture statistics for an entire field layout. For this reason, it should be linked to the main *Output* port of the object whose field statistics you wish to collect.
{% endhint %}

## **Configuring the Data Profile Object**

1. To configure the *Data Profile* object, right-click on its header and select *Properties* from the context menu.

![](/files/C3ld1bkXAcHbEECKC29p)

A configuration window will open. The first screen you will see is the *Layout Builder*. This is where we can create or delete fields, change field names, and their data type.

![](/files/3ti5bb7Pv9sScayeHnHm)

2. Click *Next*. This is the *Properties* window.

![](/files/4Jo7ckyMoIbeHJkyfkPX)

3. Here we will provide the *Profile File* path to specify where the profile should be stored.

![](/files/LkGXD2cWqoo57hsHfZ1s)

4. Specify the type of *Field Statistics* to be collected.

![](/files/WoPkG3UbopHqnF3BKbvJ)

*The Field Statistics* dropdown allows you to choose detailed levels of statistics to collect. Select among the following detail levels:

* *Basic Statistics*: This is the default mode. It captures the most common statistical measures for the field’s data type.
* *No Statistics*: No statistics are captured by the *Data Profile*.
* *Detailed Statistics – Case Sensitive Comparison*: Additional statistical measures are captured by the *Data Profile*, for example, Mean, Mode, Median, etc. using case-sensitive comparison for strings.
* *Detailed Statistics – Case-Insensitive Comparison*: Additional statistics are captured by the *Data Profile*, using case-insensitive comparison for strings.

In this case, we are collecting a *Detailed Statistics – Case Sensitive Comparison*

![](/files/J1YMhdDQ9QkJ3T5BYYFK)

Click *OK*.

## **Executing the Task**

1. After configuring the settings for the *Data Profile* object, click on the *Start Dataflow* icon from the toolbar located at the top of the window.

A *Job Progress* window will open at this instant and will show you the trace of the job.

![](/files/udHIxykxzRGyjOdrUENY)

2. Click on the *Profile* link provided in the *Job Progress* window and the profile will open in Astera. Expand the *Profile* node to see each field inside the object. Click on these fields to see the collected statistical values.

![](/files/LKooAK88sH4aOypZXsMJ)


---

# Agent Instructions: 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://documentation.astera.com/astera-data-stack-v8/dataflows/data-logging-and-profiling/creating-data-profile.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.