Running the Basic Subset Job creates a set of Subset Rules, in addition to a set of relationships that the Data Subset will need to retain or not. This information is stored in the Advanced Control Spreadsheet, where rules and relationships can be toggled on or off from the Advanced Control Spreadsheet.

You can thereby refine the Control Spreadsheet to create Subsets iteratively. This will include more or less data in your Data Subset, depending on which inter-related tables must be included to fulfil the specified relationships.

The process of running an iterative Subset involves the following actions:

  1. DROP: Drops the tables created by the PREPENV Action and deletes the data in your Target Database. You will only run this if something has gone wrong in a Subset, and you want to create a wholly new Data Subset.

    1. PREPENV: If you drop the tables, you will need to re-recreate tables before performing the next Subset.

  2. TRUNCATE: Deletes data from the Target Database or Schema.

  3. BUILDMODEL: Creates the rules to drive the Advanced Subset, based on the Control Spreadsheet.

  4. SUBSET: Writes the new Data Subset to the Staging Database.

These Actions are driven by the Advanced Control Spreadsheet. The sheets in the Advanced Control Spreadsheet are created and populated when the actions of a Basic Subset are performed. They can then be refined to run iterative Subsets.

This subsection of the Knowledge Base explains:

  1. How to refine the Advanced Control Sheet where needed in order to re-run an updated Subset job.

  2. How to perform the Actions involved in running an Advanced or Iterative Subset.