5.2.1 Flow of table design

The following shows the general procedure for designing tables:

1. Determine whether to define the table as a row store table or a column store table.

   With reference to 5.2.2 Criteria for selecting row store tables and column store tables, determine whether to define the table as a row store table or a column store table.

2. Determine whether to define the table as a single-chunk table or a multi-chunk table.

   With reference to 5.2.3 Criteria for selecting single or multi-chunk tables, determine whether to define the table as a single-chunk table or a multi-chunk table.

3. When defining the table as a row store table, assess the normalization of the table.

   With reference to 5.2.6 Normalizing a table [Row store table], assess the normalization of the table.

4. Assess the items to specify when defining the table (assess the options to specify in the CREATE TABLE statement).

   With reference to the following topics, assess each of the items to be specified in the table definition:

   • 5.2.7 Fixing the row length (FIX specification) [Row store table]

   • 5.2.8 Setting a default value for a column (DEFAULT clause)

   • 5.2.9 Specifying a primary key (uniqueness constraint definition) (PRIMARY KEY) [Single-chunk table]

   • 5.2.10 Specifying a foreign key (FOREIGN KEY)

   • 5.2.11 Allocating an unused area inside the data page (PCTFREE) [Row store table]

   • 5.2.12 Branch specification for column data of variable-length data types (BRANCH) [Row store table]

   Note

   • The label [Row store table] indicates that the item needs to be assessed when defining the table as a row store table. You do not need to assess these items when defining the table as a column store table.

   • The label [Single-chunk table] indicates that the item needs to be assessed when defining the table as a single-chunk table. You do not need to assess these items when defining the table as a multi-chunk table.

To Page Top