Control Tables

When the master script workflow name_Run.sql is run, the Control Table is created first by using the name specified in the control table name variable.

The Control Table performs the following:

• Registers generated objects, such as views, models, text specifications and so on

• Allows input objects to be looked up by the logical nodes in the workflow, and registers their output objects

• Determines the objects that need to be dropped by the cleanup script

• Provides internal name of objects that are not readily accessible through the workflows. For example, users can find the model test result tables by viewing the Control Table.

• By using different control file names along with different output variable names, you can use the generated script to concurrently generate and manage different results. This may be useful if the input data sources continue different sets of data that you want to mine independently. In this use case, the application would be responsible for saving the name of the Control Table so that it can be utilized when rerunning or dropping the generated results.

• Structure of the Control Table
  The Control Table is created first by using the name specified in the control table name variable when the master script workflow name_Run.sql is run
• Columns in the Control Table
  The columns in the Control Table contains information related to nodes and models.