Overview of the Advanced Control Spreadsheet

May 21, 2019

|By Thomas Pryce

Search Knowledge Base by Keyword

Created OnMay 21, 2019

byThomas Pryce

The following sheets will have either been contained in the initial Basic Configuration Spreadsheet, or will have been created when the Basic Subset Actions were run.

Sheet Name	Contains	Editable?	Effect of Editing
Configuration	Displays the database connection, source and target databases and schemas, max rows, max iterations and substitution parameters.	Yes	See the previous Knowledge Base article on the Configuration sheet.
FOUNDCRITERIA	Displays any FoundCriteria, used to define when the Subset should finish.	Yes	See the previous Knowledge Base article on the FOUNDCRITERIA sheet.
SQLCRITERIA	Contains the criteria used to produce the Subset results.	Yes	See the previous Knowledge Base article on the SQLCRITERIA sheet.
ForeignKeys	Displays the Foreignkeys that have been read from the source database.	Yes	Toggle Foreign Keys that will be read in future Subsets.
SoftKeys	Displays any “Soft” Primary Keys that were set for the Subset.	Yes	See the previous Knowledge Base article on the SoftKeys sheet.
Tables	Displays the metadata that has been read from the source database.	Yes	Toggles the source tables from which metadata will be read during the Subset.
RuleList	This sheet contains the rules to drive subsetting. These rules are formulated automatically from the user-defined parameters, maintain consistency and referential integrity.	No	See the previous article on the RuleList sheet.
ProcessModel	This sheet contains the model used to drive the Subset. It is populated by information in the RuleList and SQLCriteria sheets.	Yes	See the previous article on the ProcessModel sheet.
SubsetResults	This sheet displays the number of rows during Staging and the number of rows added to each Schema.	No	See the previous article on the SubsetResults sheet.
HashCodes	The sheet holds hashcodes for the SQLCriteria, Tables, ForeignKeys and SoftKeys sheets. If any of these has changed since the last BUILDMODEL action was run, the ProcessModel sheet might then be out of date.	No	The automation uses the HashCodes sheet to validate that the database model is still valid and up-to-date.

These sheets will all feature in the Control Sheet following a Basic Subset Job: