# Database Device Locations and Sizes

The Database Device Locations and Sizes dialog box must contain information about the pathnames and sizes for these tablespaces:

- Database Data Files tablespace
- Temporary Files tablespace
- Catalog Files tablespace

## Data and Index tablespaces

For the data and index tablespaces you must use a Database Managed Space (DMS) tablespace.

DMS is a tablespace where files are linked to a tablespace. The DMS tablespace size is fixed. The database administrator needs to increase the size in case the DMS tablespace is full. However, DMS offers the highest performance for the data and index tablespaces.

## Catalog and Temp tablespaces

For tablespaces which will grow and shrink dynamically such as CATALOG and TEMP tablespaces, it is recommended to use the System Managed Space (SMS) tablespace.

SMS is a table space where a directory on the system is pointed as the place to create the tablespace. An SMS tablespace will automatically increase in size in case more data must be stored.

## Data storage

This table lists a rough starting value for the size of the DB2 table spaces. Consider the requirements based on your system sizing for optimal performance.

Tablespace | Type | Initial size | Description
--- | --- | --- | ---
Catalog | SMS | Minimal 10 GB free disk space | Space for the system catalog tables. This table space is always created when the database is created.
Temporary | SMS | Minimal 10 GB free disk space | Space for tasks such as sorting
Data | DMS | Minimal 20 GB | Space for data and indexes. See your sizing report for specific information about the initial size. Note that you must specify two different data files, one for data and one for indexes. Both datafiles will be created in the same tablespace.