Target Attributes

The database label. By default, this is set to the target database filename (without the .sxv4 extension).

You can change the label if you wish, although this label is not used in the SuperSTAR clients (you can set the display name for the database to use in the clients when you add the database to the catalogue in SuperADMIN).

Whether to generate Rkeys automatically for this database. See Automatically Generate R Keys for Perturbation for more details.

The Partial Build setting determines the number of rows to include when building the database:

• If the Partial Build check box is selected then only the specified number of rows from the source database will be used for the build.
• If the Partial Build check box is not selected then all rows in the source database will be used for the build.

This option is designed to allow you to test your configuration without having to build the entire SXV4.

It is particularly useful if you have a very large source database. You can configure SuperCHANNEL to run a partial build with just a small number of rows to check that you are happy with the output. Once you are satisfied with the design of the SXV4 you can turn off the partial build and build the entire database.

When using the Partial Build option you may see errors in the logs indicating that some of the foreign key constraints did not succeed. This is typically because one of the child tables references a row in a parent table that was not included in the partial build.

The number of records channelled before changes are committed to the target database.

This setting affects disk usage. See Resource Considerations for more information.

There is also a Commit Points setting for each fact table. If this is configured at the fact table level in addition to the database level, then the fact table setting takes precedence over the setting at the database level.

The maximum number of cleansing actions allowed for a database build.

If you select the Stop on Error check box, then the build process will stop if it reaches the specified number of cleansing actions.

The default summation used during tabulation. This can be either:

• A measure column from a fact table (e.g., income, account profit, average account balance).
• A row count of a fact table (e.g., the number of customers of accounts).

The drop-down list shows all the fact tables and measure columns available in the database.

You can also tell what is currently the default summation by looking for the + icon in the Target View:

The capitalisation of the table and column labels:

When you select one of the options, all the target labels will be changed immediately. If you subsequently edit the labels, then your chosen capitalisation option will not be applied to your modified labels automatically.

If you change some of the labels and want to reapply your chosen label formatting, you must go back to the Target Attributes and reselect one of the formatting options.

The default grouping mode for the target database.

The selected grouping mode will be applied by default. You can manually modify the grouping by editing the settings in the Grouping pane. If you use the Reset Grouping option in the Grouping pane then the groupings will be reset to either flat or hierarchical based on this setting.

The display name for this table.

• For fact tables, this will be shown in the SuperSTAR clients.

• For classification tables, the label will not generally be shown in SuperSTAR clients, although it is a good idea to label a classification table so that it is easy to identify the fact table column that refers to it.

  Classification table labels are used in SuperWEB2, in the Select all at level drop-down list (although you can also change that text by configuring SuperWEB2).

• Plain tables are not included in the target database, so any label you set for these tables will not appear in SuperSTAR clients. Setting a descriptive label for these tables may help readability of the target schema.

The table type (Fact, Classification or Plain).

A SQL WHERE or ORDER BY clause that will be executed when the database build is run. For example, you might use this to sort your classification tables.

• Only drivers that support selection queries can use this function.
• Each JDBC or ODBC driver supports its own specific SQL formatting such as quote characters. You must ensure that clauses specified as conditions are in the correct format.

The following example shows a compound WHERE clause:

Any references to columns must use the column Name attribute, not the Label:

The sequence of primary keys, if the fact table has more than one primary key.

Select one of the keys in the list and click the up or down arrow to move it up or down.

The primary key sequence is important for performance reasons:

• To increase channelling performance when a primary key extends across multiple columns, sort the source data in primary key order before loading.
• When the source database table is ordered according to the compound primary key and the correct order of the primary key columns is specified for the target SXV4 table there may be increased channelling performance.
• Specifying the order of primary key columns in a compound primary key enhances channelling performance when inserting records into tables.
• SuperCHANNEL channelling performance may decrease if tables with compound primary keys have to be checked for record integrity. It is best to avoid using compound primary keys where possible.

The number of records channelled before changes are committed to the target database.

If you set this value at the fact table level, it will override any commit points configured at the database level.

Whether or not the fact table is a multi-response table.

Select the check box to configure the fact table to be a multi-response table.

Multi-response tables are indicated in the Target View with a multi-table icon:

The names of the columns used for the Code and Name.

All valid classification tables must have one column whose usage is set to Code, and another column whose usage is set to Name.

You cannot edit this from the table Target Attributes pane. To change the column usage you need to select the individual columns and specify which one is which.

Whether to allow totals for this classification table. This setting is designed for situations where it does not make sense to generate totals based on this classification (for example, you may have a time series database where it does not make sense to sum across years). The setting currently applies to SuperWEB2 only; it does not affect totals in SuperCROSS:

• Select the check box to allow totals (this is the default).
• Clear the check box to disallow totals. Users of SuperWEB2 will not be able to create a total for a field that is based on this classification table.

The seed and generator to use when generating Rkeys for this fact table. These settings only appear if the Generate Rkey Automatically check box is selected. See Automatically Generate R Keys for Perturbation for more details.

The column usage.

The column data type. You can change the data type by selecting a new value from the drop-down list:

Indicates whether or not this column is a primary key. You can also identify which columns are primary keys by looking for the key icon in the Target View.

Primary keys are used when linking tables. For example, if there are multiple fact tables, one of the fact tables must has a foreign key that is linked to the primary key of the other fact table.

In addition, each Classified column in the fact tables must be linked to the primary key of its classification table (the Code column).

Indicates whether or not the fact table column is included in the build.

Excluded columns appear in the Target View but are greyed out:

Any column with the data type OTHER is automatically excluded from the build. You will need to change the column data type in order to include it in the build.

You should always exclude columns from the build if their data is not required in the target database. This helps to optimise build times and keep database sizes to a minimum.

The action to take when the build fails to match a value in the fact table column with the set of possible values in the linked classification table.

For example, the Gender column might be linked to a classification table containing the codes M (Male), F (Female), and U (Unknown). What should SuperCHANNEL do if it encounters an empty value for this column in one of the records in the fact table?

You can choose from the following cleansing actions:

Cleansing Action	Description
Add To Classification	Add the new value to the classification table. This is the default action for classified columns. This option is only available for classified columns; it cannot be used for foreign key columns to other fact tables or between a fact table column and a multi-response fact table. If you try to set these to use the add to classification action then SuperCHANNEL will automatically revert to skip.
Bin	Convert the value to a specified "bin" value. The bin value must already exist in the corresponding classification table.
None	Do not capture exceptions. Use this action for non-SXV4 drivers.
Skip Row	Skip this record. This can be a useful cleansing action for a column linking two fact tables. For example if you want SuperCHANNEL to skip all Account records that do not have associated Customer records. Use caution when selecting this option: your target may end up with fewer fact records than the source.
Stop	Stop the build process. This is the default action for foreign key columns to other fact tables.