The following options are only in effect when new DB2 tables are created in the specified schema or when in Migration Mode. All options may be individually set. For example, you may wish to take a phased approach to very large migration projects where table definitions are created first, then data exported and finally indexes and relationships built.
Select this option to create DB2 table definitions.
Check this box to transfer Access data to DB2.
To transfer only data to DB2 tables (with associated names) that are already created, un-check all migration options except for the “Data” option. (See Load/Import Options)
Check this box to include DB2 indexes.
Check this box to include relationships.
With DB2 for OS/390 there is a combo box beneath the check box that allows you to choose whether relationships are implemented using declarative ”Foreign Keys” constraints or using “Triggers”. If you choose “Foreign Keys” then table spaces will be placed in check-pending state when the “Foreign Key” table contains data. Your database administrator must execute the DB2 for OS/390 “CHECK DATA” utility for each table space placed in check-pending state before the table can be used. The Scriptoria DB2 Viewer’s “Status” field displays the names of table spaces (by table) in check-pending state.
When relationships are implemented using “Triggers”, Scriptoria checks the integrity of the relationship before deploying the triggers. An error is issued when foreign-key tables contain one or more rows that do not have matching primary-key rows in the parent table. Note that triggers are always used to implement relationships that specify the MS-Access CASCADE UPDATE option.