There's more...
We've just covered basic commands, but there are many more aspects to discuss concerning the implementation, and some of these have an important performance impact.
Raw partitions
A container in this type of table space can be defined as a regular OS file or can be defined as a raw partition.
We do not recommend the use of raw partitions, since this adds complexity in disk and space management. A well-tuned DMS table space, that has containers defined as data files, will perform as well as containers defined as raw partitions.
Space allocation
Space is preallocated in the DMS table space. When multiple containers are defined, they are filled in round-robin fashion, one extent in each container. When autoresize
is used, the containers will grow automatically, until maxsize
value is reached, or until the filesystem is full, whichever comes first.
Tables and objects
A table can be split into multiple table spaces by:
Regular table data
Indexes
Long field and LOB data