Table of Contents

Search

  1. Preface
  2. Introduction to Test Data Management
  3. Test Data Manager
  4. Projects
  5. Policies
  6. Data Discovery
  7. Creating a Data Subset
  8. Performing a Data Masking Operation
  9. Data Masking Techniques and Parameters
  10. Data Generation
  11. Data Generation Techniques and Parameters
  12. Working with Test Data Warehouse
  13. Analyzing Test Data with Data Coverage
  14. Plans and Workflows
  15. Monitor
  16. Reports
  17. ilmcmd
  18. tdwcmd
  19. tdwquery
  20. Data Type Reference
  21. Data Type Reference for Test Data Warehouse
  22. Data Type Reference for Hadoop
  23. Glossary

Data Integrity Options in a Data Subset Plan

Data Integrity Options in a Data Subset Plan

You can create an entity and choose the method to create a subset at run time. Use the same entity to create data subsets that might contain different records by using different data integrity options at run time.
You choose the required data integrity option from the
Advanced Settings
section of the
Plan Settings
page during plan creation.
You can choose the following data integrity options based on the requirement:
Transactional Integrity for Major Relation Type
A data subset operation that includes the Transactional Integrity for Major Relation Type option might include additional records. Because of the major constraint, a child record selected for the subset operation pulls in related parent records from parent tables. The parent records select all the related child records from the child table. As more records are selected in the child table, the related parent records are selected again. This is because the records one parent selects in the child table might point to parent records that are not included in the subset. This process continues in a loop until there are no more related records to select.
For self cyclic relations and objects that have more than one major parent relation, the workflow performs recursive evaluation to compute the subset. Recursive evaluation requires a staging connection.
The operation applies the criteria on the entity as a whole and not on individual tables. If an entity contains multiple criteria, the operation uses the AND operator between criteria. If the different criteria qualify mutually exclusive tables, the subset operation might not return any data. To avoid a data subset with no records, you can edit the criteria to use the OR operator at run time from the
Criteria
page during plan creation. To edit the criteria, select
Advanced
on the
Custom
tab and configure the filter expression.
This option maintains transactional and referential integrity of the data.
Referential Integrity Only
The Referential Integrity Only option selects the least number of rows required to maintain referential integrity of data in the subset. A workflow that uses this method therefore returns fewer records than a workflow that maintains transactional integrity too. The subset might not include all child records that pertain to a parent record and therefore transactional integrity might break.
You can use this method if the entity contains a single criteria. If the entity contains more than one criteria, the workflow uses the Transactional Integrity for Major Relation type even if you choose the Referential Integrity Only type.
For self cyclic relations and objects that have more than one major parent relation, the workflow defaults to the Transactional Integrity for Major Relation type.
Two-way
A workflow that includes the Two-way option might return more records in the data subset compared to the first two options. This option maintains referential integrity and all tables that meet the criteria contain at least some data in the subset. Use this option if the entity contains multiple criteria and if you want to propagate the criteria to the entire entity.
Criteria propagates downward and then moves upward alternately until all tables in the entity are covered. The workflow uses the OR operator when the criteria moves upwards.
For self cyclic relations, the workflow performs referential looping in one direction, from child to parent tables.
If an entity contains a cyclic relationship, the workflow defaults to the Transactional Integrity for Major Relation type.
The Two-way option requires a staging connection. Based on the data and how you apply the criteria, the staging connection might or might not be used.
Consider the following points before you choose the Two-way option in a plan:
  • If you edit the entity to optimize relationships or manually change the relationship type, the changes are ignored when you choose the Two-way option in a plan.
  • If you select the Two-way option and you choose to optimize relations in a plan, the optimize option is ignored.
  • If you include custom Advanced or Limit criteria options in a plan, the Two-way option is not available.
One-way
This option applies criteria on individual tables and not the entity as a whole. The one-way option returns more data than the Two-way option. The workflow picks the least number of tables on which criteria is propagated in order to maintain referential integrity. The criteria propagates downwards. Tables above the level of the topmost table on which you apply criteria are included as is. The subset includes all data from the tables.
Use this option if you want to create the smallest required subset that does not break referential integrity, and include all data from tables above the topmost table on which you apply criteria.
For self cyclic relations, the workflow performs referential looping in one direction, from child to parent tables. Recursive evaluation requires a staging connection.
If an entity contains a cyclic relationship, the workflow defaults to the Transactional Integrity for Major Relation type.
Consider the following points before you choose the One-way option in a plan:
  • If you choose to optimize relationships or manually change the relationship type, the changes are ignored when you choose the One-way option in a plan.
  • If you select the One-way option and you choose to optimize relations in a plan, the optimize option is ignored.
  • If you include custom Advanced or Limit criteria options in a plan, the One-way option is not available.