Moves one page back in the wizard.

It is available on all but the first page of the wizard.

Moves one page forward in the wizard, except on the last page of the wizard where it is unavailable. This button may also be disabled on some pages until all required information has been entered by the user.

Starts the process that creates a database partition based on your specifications. (Available when you specify all the required input.)

Cancels any changes you have made to this wizard and closes the wizard.

Type an identifier for the table space that you are creating. This identifier:

Optional: Type a description of your table space for clarification. The description can be 1 - 30 characters in length.

The description will appear as a comment in the details view of the table spaces.

You can change the comment later using the Alter Table Space notebook.

Specifies that the table space that you are creating can contain any type of data except temporary tables.

If you opened the Create Table Space wizard from the Create Table wizard, and you chose to create a regular table space, this radio button is selected by default and cannot be changed.

A database should also have at least one regular table space.

Specifies that the table space that you are creating can contain long or LOB data such as images, audio, video, or long text fields.

When this radio button is selected, High performance is the only option on the Management page.

If you opened the Create Table Space wizard from the Create Table wizard, and you chose to create a separate large space, this radio button is selected by default and cannot be changed.

Specifies that the table space that you are creating can be used by the database manager for temporary tables created during sorts, joins, and other operations.

A database must have one temporary space. You can create more, but for most situations only one is required. The default temporary table space is called TEMPSPACE1.

Specifies that the table space that you are creating can be used to store declared global temporary tables. User temporary table spaces are not automatically created during database creation.

Select the database partition group that includes the database partitions on which the table will reside.

Shows the number of database partitions in each database partition group.

Lists the names of the database partitions within each database partition group. For example, "0, 2, 4 to 8"

Opens a window in which you can create a new database partition group.

Shows existing buffer pools.

Shows the number of pages that each buffer pool contains. The number of pages is a measure of how much memory is in the buffer pool (that is, the size of the buffer pool). You can calculate the total amount of memory in the buffer pool using: number of pages * page size. For example, 250 pages * 4 KB/page = 1000 KB = 1 MB

The default number of pages is 250 (except for Unix platforms, where it is 1000).

Shows the size of the pages used for each buffer pool. The valid values are 4 KB, 8 KB, 16 KB, and 32 KB. The default page size is 4 KB. Selecting a buffer pool with a larger page size allows you to create a table space with the same page size.

Opens a window in which you can create a new buffer pool.

Shows the amount of disk space allocated for one row of regular table data.

Specifies that the new table space will be managed by the operating system. Advantages of a system-managed space (SMS) table space:

In general, small personal databases are easiest to manage with SMS table spaces.

Temporary table spaces should be SMS table spaces since their size can grow and shrink as needed. This reduces unnecessary temporary space and reduces the possibility of running out of temporary space.

Specifies that the new table space will be database-managed. Advantages of a database-managed space (DMS) table space:

Opens a window so that you can add items to the list.

Opens a window so that you can make changes to the selected item.

Removes the selected item from the list.

Click on the arrows below to expand the view so that you can see the container paths for each database partition.

Shows the names of containers used for the table space.

Shows the type of each DMS container.

For DMS table spaces, shows the size of each container.

Shows the database partitions on which the containers reside.

Shows the amount of disk space allocated for this DMS table space, which is the sum of all containers defined.

Specifies the unit size to use for this DMS table space.

Specifies that the average size of a table in this table space will be less than the value shown in the wizard. The system recommends an extent size of 8 pages.

You can calculate the size of a table by multiplying the byte count of a single row by the number of rows in the table. A rough estimate is all that you need.

The extent recommendation is based on the fact that smaller tables are more efficiently stored in smaller extent blocks.

Specifies that the average size of a table in this table space will be in the range shown in the wizard. This is the default setting. The system recommends an extent size of 16 pages.

You can calculate the size of a table by multiplying the byte count of a single row by the number of rows in the table. A rough estimate is all that you need.

The extent recommendation is based on the fact that smaller tables are more efficiently stored in smaller extent blocks.

Specifies that the average size of a table in this table space will be in the range shown in the wizard. This is the default setting. The system recommends an extent size of 32 pages.

You can calculate the size of a table by multiplying the byte count of a single row by the number of rows in the table. A rough estimate is all that you need.

The extent recommendation is based on the fact that smaller tables are more efficiently stored in smaller extent blocks.

Specifies that the average size of a table in this table space will be greater than the value shown in the wizard. The system recommends an extent size of 64 pages.

You can calculate the size of a table by multiplying the byte count of a single row by the number of rows in the table. A rough estimate is all that you need.

The extent recommendation is based on the fact that smaller tables are more efficiently stored in smaller extent blocks.

Type a number in this field or use the spin buttons to specify the number.

The number in this field multiplied by the extent size is the recommended prefetch size.

The prefetch recommendation is based on the fact that if you have containers on separate physical drives, the database can prefetch from all of those drives at the same time.

Specifies the recommended extent size settings based on the answers that you provide in the Determining recommended settings group box.

An extent is an allocation of space, within a container of a table space, to a single database object. This allocation consists of multiple pages.

You can also change the Extent size field directly by typing a number in this field.

Specifies the recommended prefetch size settings based on the answers that you provide in the Determining recommended settings group box. The numbers are based on factors and multiples of the extent size.

Prefetching reads the data needed by a query before it is referenced by the query, so that the query does not have to wait for I/O to be performed.

You can also modify the Prefetch size field directly by clicking the down arrow to display the list of valid prefetch sizes and selecting one.

Specifies the drive specifications for a typical server with SCSI-controlled hard drives. If you know the exact drive specifications for your system, type the values in the fields found in the Specifications group box.

Selecting this option will set the drive specifications for a typical high-performance server configuration. If you know the exact drive specifications for your system, type the values in the fields found in the Specifications group box.

Selecting this option will set the drive specifications for a typical RAID (Redundant Arrays of Independent Disks) configuration. If you know the exact drive specifications for your system, type the values in the fields found in the Specifications group box.

Selecting this option will set the drive specifications for a typical storage area network configuration. If you know the exact drive specifications for your system, type the values in the fields found in the Specifications group box.

Specify this option if you are using an advanced storage system other than those previously listed. Type the calculated values for your system in the fields found in the Specifications group box.

Specifies the average time it takes for the disk head to locate data on the disk. If you have exact specifications from the manufacturer, you can type the value in this field.

The value in this field is used to calculate the overhead setting.

Specifies the number of rotations per minute for the disk. If you have exact specifications from the manufacturer, you can type the value in this field.

The value in this field is used to calculate the overhead setting.

Specifies an estimate of the time it takes to read one page of data into memory. If you have exact specifications from the manufacturer, you can type the value in this field. Transfer rate is also known as "sustained data rate" or "sustained throughput". Do not use the "maximum interface transfer rate".

The value in this field is used to calculate the transfer setting.

The overhead value is calculated from the values in the Average seek time, Rotation speed, and Transfer rate fields in the Specifications group box, which are recommended based on the answers that you specify in Determining your specifications and calculated settings.

This value is calculated using the following formula:

overhead = average seek time + ( ( ( 1 / rotation speed ) * 60 * 1000 ) / 2)

If you calculated the settings manually, you can type the value in this field.

The transfer value is calculated from the values in the Average seek time, Rotation speed, and Transfer rate fields in the Specifications group box, which are recommended based on the answers that you specify in Determining your specifications and calculated settings.

This value is calculated using the following formula:

transfer = ( 1 / transfer rate ) * 1000 / 1 024 000 * 4096 (assuming a 4KB page size)

If you calculated the settings manually, you can type the value in this field.

Select to enable dropped table recovery if your tables contains data that must not be lost. For a dropped table to be recoverable, the table space in which the table resides must have this option turned on. Using dropped table recovery, you can recover your dropped table's data by performing a table space level restore and roll forward. This method is faster than a database level recovery and allows your database to remain available to the users.

Note: If your application creates and drops many tables in a regular table space, this may cause the table space's performance to degrade.

Opens the Show SQL window.