A reset operation does not delete records in master tables. It performs an upsert on master tables. When testers share all records in a table, classify the table as a master table. Because the reset does not delete records in master tables, the reset operation does not delete records that might impact the work of other testers.
Classify tables that are descendants of master tables as transactional tables. Records in transactional tables are generally not shared records. When you delete a record, you do not impact the work of another tester. By default, during a reset operation TDM performs an insert on transactional tables. You can choose to change the default behavior when you configure the reset operation.
If you do not classify a table, by default a reset operation considers the table as a transactional table.
TDM performs the following tasks during an upsert:
Updates records that exist in both the data set version and the target.
Inserts records that are present in the data set version and not in the target.
During an insert, TDM inserts records from the data set version that do not exist in the target. If the record exists, the insert fails.
Based on how you classify tables as master and transactional, TDM identifies top-level transactional tables and begins the cascade delete at this level.
A top-level transactional table is a direct child of a master table. All parents of a top-level transactional table, if any, are master tables.
Verify the table classification before you perform a reset operation.