[Net 2000 Ltd. Home][DataBee Home][DataBee Manual][DataBee FAQ]
The DataBee Set Designer
Rule Tools Tab
The Rule Tools Tab has two primary functions: to launch tools which download schema information from the database
and to launch other tools which assist with the identification of relationships
between tables.
The section on the top right is entitled Get Information from Source
Schema and contains the buttons that launch tools that query the remote database for information.
The section on the top left is entitled Useful Tools provides a number of useful tools to manipulate the
schema information already in the Extraction Set. The tools in this section can also be used to discover new rules
from the schema structure.

The DataBee Set Designer Rule Tools Tab
Get Information from Source Schema Section:
The Set Designer application needs to be made aware of the configuration and components in the
source schema (tables, columns, column sizes, foreign key constraints etc.) before it can be used.
This information must be acquired from the source database for each schema listed in the Extraction Set.
What the buttons do
- Get Schema Information from DB
- This button launches a tool that will download the schema information (tables, columns etc)
from the source database of the selected user. This is a very important tool and needs to be used before any rules can
be defined. Detailed information on this tool can be found on the
Get Schema Information help page.
- Generate Rules from DB Constraints
- Many Oracle database schemas contain referential integrity constraints which define relationships
between tables. If such constraints exist in the remote database the Extraction Set will need to contain
rules which enforce them. If integrity constraints are present in the database but not in the Extraction
Set then the DataBee Set Extractor application will
not be able to take them into account when deciding which rows to extract from the database.
In such a case it is highly probable that the referential integrity constraints will not be able to be
applied to the destination database when the extracted data is eventually loaded. Detailed information
on this tool can be found on the
Generate Rules from DB Constraints help page.
- Get Table Row Counts from Schema
- When designing Extraction Sets it is useful to know the number of rows in each table in the source schema and
also to be able to get a summary of the number of rows last extracted for each table by the set. The
Get Table Row Counts from Schema tool enables the number of rows in each table in the source schema to
be acquired and stored with the Extraction Set. It also contains a reporting feature which enables sorted
lists of row counts to be produced. More information on this tool can be found on the
Get Table Row Counts from Schema help page.
Tools Section:
The buttons in this section launch tools that can discover relationships between the schema tables. These tools
can only act upon information already known to the Set Extractor application. The schema information must be
retrieved from the source schema into the Set Designer application before any of these tools will work (see above).
What the buttons do
- Column Finder
- In order to join two tables together with an extraction rule, the join column (or columns) must be
known. The function of the Column
Finder tool is to search through all tables in the schema for columns of a specified name, size or data type
in order to find possible candidates for a rule.
Detailed information on this tool can be found on the
Column Finder help page.
- Who-Loads-What
- The Set Extractor application will use the rules in the Extraction Set to make sure that the appropriate
data rows are retrieved from each table in order to support the rows in the other tables. As rules are
added to the Extraction Set the relationships between them become increasingly complex and
any one table may populate or be populated by a number of others. The Who-Loads-What tool is
designed to show the tables which load a specified table and those which are loaded by the table. Detailed information
on this tool can be found on the
Who-Loads-What help page.
- Chain Finder
- The the Chain Finder dialog box provides a visual indication of the relationships between tables
and suggests possible candidates for manual rules. It presents a list of all tables known to the Set Designer
application and the number of direct descendant child tables the current rules associate them with. Also shown
is a tree structure providing a graphical representation of the tables relation to the other tables in the
Extraction Set. Detailed information
on this tool can be found on the Chain Finder help page.
- Generate Reverse Tails Rules
- Tables which require data rows to be present in other tables (outgoing rules), but have no rules
from other tables which require rows in them (incoming rules) will never contribute any rows to the
Extracted set. The Generate Reverse Tails Rules tool is
designed to suggest incoming rules which will populate these tables and make their outgoing rules more effective.
Detailed information on this tool can be found on the
Generate Reverse Tails Rules help page.
- Index Follower
- Tables are often indexed on the most important columns. The Index Follower
dialog box allows you to pick a table and then discover potential rules based
on joins via indexes. Detailed information on this tool can be found on the
Index Follower help page.
Misc. Section:
What the buttons do
- Test/Create Temporary Table
- The DataBee Set Extractor application requires a temporary table in the source schema to assist with
the extract of the data. This button tests for the existence of this table and enables its creation - if
required.
- Check for Unindexed Rule Targets
- If the target table in a rule has join columns that are unindexed, then the rule
can sometimes be slow to extract - particularly if the table has a large number of
rows. The Unindexed Rules Detector tool identifies such rules and offers the facility
of deleting or disabling them.
[Net 2000 Ltd. Home][DataBee Home][DataBee Manual][DataBee FAQ]