> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/data-model/data-vaults/data-vault-automation.md).

# Data Vault Automation

Data vault modeling can be time-consuming when dealing with many entities in a data model.

Astera Data Stack's *Build Data Vault Model* feature swiftly automates the data vault modeling process of your OLTP system.

Using this feature provides users with a good starting point to further model their data vault.

### **Overview**

1. The first step is to *Reverse Engineer* a database. To learn more about *Reverse Engineering* in Astera Data Stack, click [here](/data-model/data-models/reverse-engineering-an-existing-database.md).
2. Once a database has been reversed engineered, the entities will be set as general entities by default. To convert this data model into a data vault, these entities need to be changed according to their attributes, into Hubs, Links, and Satellites.
3. To use the data vault automation algorithm, select *Data Model -> Build Data Vault Model* from the *Data Model* drop-down menu.

![](https://content.gitbook.com/content/zEifS4h8yurLAAwiGNX2/blobs/14Ht9nGsrAYcaW16wO7s/clip_image002.png)

{% hint style="info" %}
**Note:** Before the *Build Data Vault Model* option can be implemented, you will be asked to save the data model.
{% endhint %}

4. Upon selecting the *Build Data Vault Model* option, the *Select entities* screen will prompt you to select entities required to be modeled into a data vault. Entities can also be searched using the search bar, and filtered based on entity name and schema, using the filter option. Once you have selected the entities to be modeled, click *OK*.

![](https://content.gitbook.com/content/zEifS4h8yurLAAwiGNX2/blobs/p9MtvokmEQFTFx5RXXPd/clip_image004.png)

5. For this use case, we have selected all the entities. Once done, a data vault of these entities will be generated as a separate data model. This allows users to keep the source and data vault model separate. Each data vault entity will automatically have [data vault roles](/data-model/data-vaults/raw-vault-entities.md#data-vault-roles-in-astera-data-stack) assigned to each field, along with appropriate relationships between entities.

![](https://content.gitbook.com/content/zEifS4h8yurLAAwiGNX2/blobs/lnvNvLpzwKy7rE7z74E3/clip_image006.png)

The data vault automation feature does not simply create Hubs, Links, and Satellites for every underlying entity, but also models different kinds of relationships, such as self-relationships, many-to-many relationships, unit of work relationships, and multiple relationships between entities.

It can also create Satellites on Hubs and Links based on the primary key or combination of primary keys that are described by the attributes of the underlying entity.

This functionality essentially provides users with a starting point, wherein it gives us a basic vault model that we can make further changes to, based on our specific requirements. 


---

# 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://documentation.astera.com/data-model/data-vaults/data-vault-automation.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.