The DataBee Set Extractor application will connect to each schema and extract the relevant rows according to the rules defined in the Extraction Set. Extraction Sets are created and modified using the Set Designer application. Only the Source user information is required - the Set Extractor application expects to be able to connect to these users to access the tables they contain. The Destination user is not used - it will be accessed by the Set Loader application when the Extracted Set rows are loaded into the destination schemas.

The DataBee Set Extractor Known Schemas Tab

The panel on the top of the Known Schemas Tab lists the schemas in the Extraction Set. The current version of DataBee can configure an Extraction Set for up to 64 separate users. To see the details on a user click on the schema name with the mouse and press the Update User button.

The User Information panel contains the buttons which can add, discard, modify or test the connection details for each schema in the Extraction Set. The button will operate on the schema currently selected in the top panel.

The Set Information panel contains the name of the currently loaded Extraction Set. This is the filename that is the container for the various component files and contains information on all users in the Extraction Set. These components are designed to be used in a modular fashion. Component files can be changed in the Set Designer application as required to configure different variants of an Extraction Set.

Connection Information File

This file contains the source and destination connection information that is displayed in the top panel. This information created in the Set Designer application but can be modified via the use of the Update User button.

Schema Information File

All of the table information (table name, and column information) is contained in this file. If the source schema is upgraded this is the file that will need to be updated or changed. This information is created and updated via the Get Tables from Schema dialog box.

DB Constraint Rule File

Most Oracle databases enforce some sort of referential integrity using foreign key constraints. Rules based on these constraints are kept separate from manually entered Extraction Set rules. If the schema changes and new foreign key constraints are added or dropped this file will need to be updated or changed. This information is created and updated via the Generate Rules from DB Constraints dialog box in the Set Designer Application.

Custom Rule File

An Extraction Set based entirely on foreign key constraint rules is unlikely to be satisfactory. Almost always custom rules will have to be manually added. This file contains those rules. It is quite possible to keep a number of variants of these files (each for a different purpose) and to substitute them as required. This information is created and updated via the many Rule Tools in the Set Designer Application.

Row Count File

The count of the rows in each table in the source schema is quite useful information to have when designing an Extraction Set. It would be very inefficient to retrieve these from the source schema each time they are required. The Row Count file contains stored row counts - it may need to be refreshed occasionally. This information is created and updated via the Get Table Row Counts dialog box in the Set Designer Application.