[Net 2000 Ltd. Home][DataBee Home][DataBee Manual][DataBee FAQ]
The DataBee Set Designer
Misc. Setup Tab
The options on the Misc. Setup tab of the Set Designer application exist to modify the actions of an open extraction set.
Note: the Set Designer software is modal - it operates on both extraction and loader sets and the options on the screen display will change as is appropriate to the type of set being configured. This help file discusses the contents of the Misc. Setup tab when the Set Designer is operating on a extraction set. For information about this tab when the Set Designer is operating on a loader set please see the Loader Set Misc. Setup tab help file.
The Set Designer Misc. Setup Tab
- Extraction Set Options
- Global Extraction Rule Hint
- This hint is applied to all SQL statements that extract rows in the Set Designer application. Usually this hint is unnecessary and the option exists primarily to be used when advised to do so by the DataBee support team.
- Test connections before running extraction set
- If checked, the login details for all Rule Controllers will be tested before any extraction rules are executed. This option is useful if the extraction set is configured with multiple Rule Controllers as it can prevent a login failure resulting in a partially run extraction set.
- Suppress no rows in stage 2 warning
- Usually the stage 1 rules extract the base data upon which the Table-To-Table rules in stage 2 will operate. If no rows have been extracted in stage 1 then there is no data for the stage 2 rules to use and the Set Designer flags this as an error. This option suppresses the raising of this error. For more information please see the Handling the No Rows In Stage 2 Error help file.
- Perform post extract validity check
- This option causes the Set Designer software to perform a referential validity check after the extraction operations complete. The validity check takes time and is usually not required.
- Single thread stage 1 rules
- This option causes all stage 1 rules to execute in a single thread rather than using the maximum number of threads set on the Set Extract Run Statistics tab. All rules will still execute in rule block order - however no rules can execute simultaneously. This option is usually only activated on the advice of the DataBee support team.
- The normal method of operation for the DataBee Set Designer software is for each thread to make and hold open a connection to the target schema. This connection is used by all rules running on the thread and is only closed when the extraction set run is finished. Under some circumstances it is better to have each rule connect and disconnect rather than using a pooled set of connections. This option is slower since it requires to overhead of making a connection for each rule but can be useful if network timeouts or other errors such as ORA-03113 End of file on communication channel are being received.
- Each rule makes a new connection
- Normally each working thread connects to the source database and stays open for the duration of the run of the extraction set. Checking this option will cause the connection to be opened and closed for each rule. Reconnecting for each rule is much slower since it introduces considerable overhead. However in some situations it can be useful in order to prevent connections with long running rules from being closed by other processes on the server while they are still in use. Probably this options should only be activated when advised to do so by a Net 2000 Ltd. support team member.
- The Number of Rule Worker Threads Setting
- The Number of Rule Worker Threads combo-box offers the option of increasing or decreasing the number of workers available for simultaneous operations. Although the number of worker threads can be changed in the Set Extractor application, this information cannot be saved back to the extraction set in that application as the Set Extractor does not have that capability. This area in the Set Designer application is the only option which can permanently change the number of Rule Worker Threads and save it to the extraction set. The most effective number of workers to use depends on a number of factors: the speed and memory of the PC on which the Set Extractor application is running, the speed of the network connection to the remote Oracle database, the speed of the Oracle database and number of CPU's on the Oracle database platform. As a general rule, it is inefficient to set the number of workers too high since bottlenecks will occur that can cause the total execution time to be longer than if fewer workers were running. Since the correct setting depends on a number of variables, finding the most effective setting is something of a trial and error process. A typical setting would be to set the number of worker threads to be equal to the number of CPU's on the Oracle database server.
The Set Designer Misc. Setup Tab Extraction Report Options
- Extraction Report Options
The two extraction statistics reports which can be generated using the Extraction Rule Statistics Report and Extraction Table Statistics Report buttons below can also be automatically generated when the extraction set completes.
- Write the report to the logfile
- If checked, the report contents will automatically be emitted to the logfile upon completion of the extraction set run.
- Write the report to the directory below
- If checked, the report contents will automatically be emitted to the specified directory upon completion of the extraction set run. The file name used is a concatenation of the extraction set name and the date.
- Actions
- Show Notes Splash Screen
- Immediately displays the notes splash screen. This can be used to review the contents of the extraction set notes.
- View Log File Now
- Each time the Set Designer application starts it creates a new log file in which it records its actions. This button will open the current log file in a text editor.
- Extraction Rule Statistics Report
- Launches a form which provides the ability to save a report listing the statistics of the rules in the current extraction set run. A rule statistics report could be used to provide a permanent record of the execution of the rules.
- Extraction Table Statistics Report
- Launches a form which provides the ability to save a report listing the statistics of the tables in the current extraction set run. A table statistics report could be used to provide a permanent record of the number of rows extracted for each table.
- Configuration Details
- Directory for Log Files
- The Set Designer application writes out various informational messages to a log in order to record its progress. A new log file is created each time the application starts and this field indicates the directory in which the log files will be placed.
[Net 2000 Ltd. Home][DataBee Home][DataBee Manual][DataBee FAQ]