Tablespaces
Go Up to Supported Objects
Tablespaces are storage structures that act as partitions for the database. You can create a tablespace to store table data and other objects related to table performance such as indexes or large object data. Tablespaces are used to manage large complex databases. Once you have created a tablespace, you can place objects on it.
- Tip: Create separate tablespaces for your tables and indexes and put each tablespace on a different drive or file system. Segmenting tables and their corresponding indexes in this manner helps eliminate I/O contention at the server level.
- Note: IBM DB2 for Linux, Unix, and Windows lets you assign a location for table or index data directly to physical storage devices. Each tablespace can also be broken down into a collection of containers which are the actual physical storage files or devices. You can then spread the data or database objects across multiple file systems, thereby giving you the necessary space for objects that require it.
Once you have created a tablespace, you can place individual tables and indexes on it. Because tablespaces map to physical drives, you can improve i/o performance by placing tables and their indexes on physically separated table spaces.
Creating and editing
- Tablespaces Wizard (Oracle) and Tablespaces Editor (Oracle)
- Tablespaces Wizard (PostgreSQL) and Tablespaces Editor (PostgreSQL)
DBMS platform availability and object actions/operations supported
The following table lists object actions available for this object type. For an introduction to object actions and details on usage of specific actions, see Object actions.
| DB2 LUW | DB2 z/OS | ORCL | PSTGRS * | |
|---|---|---|---|---|
|
✓ | ||||
|
✓ |
| |||
|
✓ |
| |||
|
✓ |
✓ |
✓ |
✓ | |
|
✓ |
✓ |
✓ |
✓ | |
|
✓ |
| |||
|
✓ |
||||
|
✓ |
| |||
|
✓ |
✓ |
✓ | ||
|
✓ |
||||
|
✓ |
✓ |
✓ |
| |
|
✓ |
||||
|
✓ |
||||
|
✓ |
||||
|
✓ |
||||
|
✓ |
||||
|
✓ |