To search the Data Vault from the entity level and to automatically create entities for data discovery, you must add constraints to the ILM repository. You can add constraints to the repository when you import metadata from a source database or you can add them manually.
When you search the Data Vault from the entity level, the entity that you search on must have the relationships required to the associated tables to show related information at the transaction level.
To create entities for data discovery, you use the
Multiple Entity Creation
wizard. The wizard uses the constraints in the ILM repository to generate the entities. The wizard adds all related child tables for the parent table you select and adds all related tables to the entity. For more information, see
Automatic Entity Generation.
You do not need constraints to archive data. When you run an archive or retirement job, the ILM engine creates a WHERE clause that determines the data to archive.
The ILM repository stores constraints for source metadata. Data Archive stores primary, referential, and unique constraint types. When you import metadata from a source database to the ILM repository, all constraints that are defined on the database level are imported. If the source database does not include constraint information at the database level, such as in the application level, then you must add the constraints to the ILM repository. You can add constraints manually. Or, you can use tools to help you discover table relationships and create constraints based on the suggested relationships.