● Journal Table (WITH JOURNAL TABLE): Specifies the name of the journal table in the format database_name.table_name. If the database name is not specified, the default database for the current session is assumed. If a default journal table was defined for the database, then this option can override the default. The journal table stores an image of the table before initiating a transaction. If the transaction completes successfully, the journal is deleted; if the transaction fails, the journal data is used to perform a rollback.
● Before Journal (BEFORE JOURNAL): Specifies the number of before change images to be maintained. If the JOURNAL keyword is specified without NO or DUAL, then a single copy of the image is maintained unless FALLBACK is in effect or is also specified. If journaling is requested for a table that uses fallback protection, DUAL images are maintained automatically.
● After Journal (AFTER JOURNAL): Specifies the number of after-image to be maintained for the table; any existing images are not affected until the table is updated.
● Freespace: Specifies percent free space (between 0 and 75) that remains on each cylinder during bulk data load operations on this table. This reserved space helps to avoid row migration and chaining caused by an update operation that extends a data row's length. Tables that won’t be updated should have this value set to 0.
● Datablock Size: Specifies the maximum data block size for blocks contain multiple rows. Larger block sizes enhance full-table scans by selecting more rows in a single I/O; smaller block sizes are best for transaction-oriented tables to minimize overhead by retrieving only what is needed. The maximum data block size is 127.5 Kilobytes.
● Duplicate Row Control: Specifies whether or not duplicate rows are permitted. Specify Set to disallow duplicate rows and Multiset to allow duplicate rows.
● Checksum (CHECKSUM): Checksum detects and logs disk I/O errors. The choices available determine the percentage of data used to compute the checksum for the table. This is an example of the SQL generated with Checksum > Medium has been selected on the Storage tab of the Table Editor.
Checksum = Medium
● Fallback Protection (FALLBACK): Select this option to implement software fault tolerance which copies the primary table to create a duplicate copy.