The Test Data Store component is the Fabric ETL and storage layer, and it is mandatory on each task. It has 2 attributes:
Check the checkbox to create a Data snapshot (version) for the extracted entities and/or tables.
This checkbox is clear by default. The checkbox can be checked whenever the Source' Policy for fetching data gets the data from the source environment or the task synthetically generates new entities.
This checkbox is checked since each task execution that gets the data from the source environment, creates a new data snapshot (version) on each extracted table.
The retention period is set on the extracted entities and/or tables. When this period ends, the task's entities and/or tables are automatically deleted from Fabric and are no longer available.
Do not delete - do not delete from Fabric.
Do not retain - avoid saving the task's entities and/or tables in Fabric. This option can be used, for example, for running an extract task on a large subset of entities in order to populate TDM parameter tables on each entity without saving the entities into Fabric.
Setting a time measuring unit (e.g., minutes, hours, days) and a corresponding value. For example, save the data in Fabric for 2 days. When this set period ends, the data will automatically be deleted from Fabric.
Notes:
The Test Data Store component is the Fabric ETL and storage layer, and it is mandatory on each task. It has 2 attributes:
Check the checkbox to create a Data snapshot (version) for the extracted entities and/or tables.
This checkbox is clear by default. The checkbox can be checked whenever the Source' Policy for fetching data gets the data from the source environment or the task synthetically generates new entities.
This checkbox is checked since each task execution that gets the data from the source environment, creates a new data snapshot (version) on each extracted table.
The retention period is set on the extracted entities and/or tables. When this period ends, the task's entities and/or tables are automatically deleted from Fabric and are no longer available.
Do not delete - do not delete from Fabric.
Do not retain - avoid saving the task's entities and/or tables in Fabric. This option can be used, for example, for running an extract task on a large subset of entities in order to populate TDM parameter tables on each entity without saving the entities into Fabric.
Setting a time measuring unit (e.g., minutes, hours, days) and a corresponding value. For example, save the data in Fabric for 2 days. When this set period ends, the data will automatically be deleted from Fabric.
Notes: