The DataBee New Extraction Rule Form

The New Extraction Rule form enables the manual creation of various types of extraction rule in an extraction set. There is an equivalent form, called the New Loader Rule form which offers similar options for loader sets. The options on this form are not the only method of creating extraction rules. The tools on the Set Designer Rule Tools tab offer automated ways of discovering and creating extraction rules.

There are a number of documents and help files which will help you learn about the DataBee software. The About the Extraction and Load Process help file discusses how the rules are configured in the extraction and loader sets to create a referentially correct subset database and the Quick Start Guide is a really useful step-by-step introduction to the DataBee software and contains links to a number of interactive tutorials.

Important Note: The DataBee software is multi-threaded and will run multiple rules simultaneously. Some types of rule (Command, All Rows and Where Clause) can execute in either stage 1 or stage 3 of the extraction process. For those types of rule please be aware that rule blocks must be used to explicitly specify the execution order of the those rules in order to control the execution sequence.

The DataBee Support team is always happy to provide advice and assistance (yes, even for an evaluation copy). If you need help please email us at Support@Net2000Ltd.com.

All extraction operations performed by the DataBee software are specified in the form of rules, called extraction rules, which dictate the actions taken. In order to choose the appropriate type of extraction rule for a particular task it is essential to understand both the requirements of the task and also the uses of the various extraction rules. Below are a list of links to the help files on each specific extraction rule type.

Table-To-Table Rules

A Table-To-Table Rule uses a join condition to extract referentially related rows from a target table for the rows previously extracted from a source table.

Where Clause Rules

Provide the initial driver data for a subset database. All of the other data extracted for the subset database will be related, directly or indirectly, to these rows.

All Rows Rules

Some tables, such as reference tables, must be extracted in full even if all of the rows are not explicitly required to support data in other tables. All Rows rules make it possible to extract, in full, all rows from a specified target table.

Command Rules

This type of rule is used to run user defined SQL or PL/SQL statements within the target database.

Rule Controller

A Rule Controller contains login information. Rule Controllers tell their dependent extraction rules which database and schema they should connect to in order to perform their actions. All other extraction rule types must have a parent Rule Controller and every extraction set must contain at least one Rule Controller.

Important Note: The first Rule Controller is created when the extraction set is built. Most extraction sets will only ever need one Rule Controller. If it is required to connect to a second schema within the same extraction set (rather than just building a second extraction set) then additional Rule Controllers can be created. The use of multiple rule controllers in an extraction set is an advanced topic and it is strongly suggested that advice and assistance is obtained from the DataBee support team prior to implementation.