Creating and configuring table spaces within automatic storage databases

Let's start by discussing the physical implementation of table spaces.

The way your data is structured, and its storage, should follow a well thought-out plan. In order to make this plan work for you, it is best to clearly understand what the underlying components are and how we can exploit them for reliability and performance.

Automatic Storage means the database takes charge of containers. Containers will be allocated and extended as needed, without intervention from the DBA. The table space type (SMS or DMS) is determined automatically.

Getting ready

Table spaces will be striped across storage paths, so you may need to have all storage paths ready.

How to do it...

1. Get current database parameters:

   	db2 => connect to nav;
   
   	   Database Connection Information
   
   	 Database server        = DB2/LINUXX8664 9.7.4
   	 SQL authorization ID   = DB2INST1
   	 Local database alias   = NAV
   
   	db2 => GET DB CFG;
   
   	       Database Configuration...