Advanced Parameters (Customizing)
Use the following parameters to customize the selected data source before you clone it. Configuration file parameters are included in parentheses.
Global data set options
Clear duplicate records encountered during data extraction (clr_dup_extr_recs)
Removes false duplicate records caused by long cloning of an active DMSII database, allowing the index creation and fixup phases to continue. If false duplicate records aren't manually removed, index creation fails. This parameter globally sets the ds_options bit that corresponds to the data set property Clear Duplicate Extract Records for all DATASETS table entries.
Force AA Values as indexes (force_aa_value_only)
Always Force forces the define and redefine commands to use AA values as the index, even if the data set has a SET that qualifies for use as an index. Force only if RSN forces the define and redefine commands to use RSN values as the index. This parameter globally sets the ds_options bit that corresponds to the data set property Use AA Values (or RSNs) as Keys for the DATASETS table entries.
Ignore new columns (suppress_new_columns)
Prevents the entire data set from being recloned because a DMSII reorganization added new items that you are willing to discard. The redefine command sets the active columns to 0 for DATAITEMS and DATATABLES entries associated with the reorganization. This parameter globally sets the ds_options bit that corresponds to the data set property Ignore New Columns for all DATASETS table entries.
Optimize column updates (optimize_col_updates)
The optimize_col_updates parameter specifies whether the define or redefine command should set the DSOPT_Optimize_4_CDC bit (value 1) in the ds_options field of the DATASETS table. This bit indicates that client will optimize column updates to eliminate changes to columns whose values are unchanged. To do this, stored procedures are abandoned in favor of pure SQL without the use of host variable. This usually slows the update speed of the Client, but the overall process ultimately takes less time because SQL Server or Oracle replication sends signficantly less data to the remote database.
Caution: Using this parameter will significantly slow update processing by the Client. If you are replicating your relational database, enabling this feature may provide some benefit if replication is very slow.
Optimize SQL updates (optimize_updates)
Deletes all redundant updates. Use this option when the number of occurrences for items is very large and you aren't you are not flattening the OCCURS clauses. An OCCURS clause is a DMSII construct that describes the number of times an item is present in a data set. This parameter globally sets the ds_options bit that corresponds to the data set property Optimize SQL Updates for all DATASETS table entries.
Split variable format data sets (split_varfmt_dataset)
This option provides an alternate way for mapping variable format data sets to tables in the relational database. The fixed parts of all variable format records are stored in the table for type 0 records. The variable parts of the records and keys are stored in tables for other types of records.
The client normally stores each record type in a table whose name is the data set name (in lower with all dashed changed to underscores) followed by "_typennn" (where nnn is the variable format record type). The table for type 0 records, which have no variable part, does not have a suffix like the tables for all other record types.
This parameter globally sets the ds_options bit that corresponds to the data set property Split variable format data sets for all DATASETS table entries.
When this option is not selected, each individual record type in the variable data set is mapped to a separate secondary table.
Flatten all OCCURS (flatten_all_occurs)
Creates a new column in the primary table for each OCCURS item. Select this option if the DMSII data doesn't contain a lot of OCCURS clauses. When unselected, a cloned DMSII data set that has an OCCURS clause in an item results in two tables in the relational database.
Maximum columns in tables (maximum_columns)
Select this option to limit the maximum number of columns that can be created in split tables. Split tables are created from a data set that exceeds the maximum number of columns allowed by the relational database. For SQL Server, this number is 1024. If you set this parameter to 1000, the split will occur after 1000 columns.
Use clustered indexes (use_clustered_index)
Select to use clustered indexes for all tables. To override this option for a single table, deselect the Use Clustered Index check box in the table properties. Applies only to SQL Server.
Use Primary Keys (use_primary_key)
Creates a primary key instead of using a unique index for all tables. To override this option for a single table, deselect the Use Primary Keys check box in the table properties.