If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Table Space for Indexes

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 11-23-11, 06:19
db2champ db2champ is offline
Registered User
 
Join Date: Jul 2011
Posts: 46
Table Space for Indexes

Hi,
What is the best approach for storing Indexes:-
(1) Index should be store same database data table space?

(2) We should create separate table space for indexes, and it should be separate for every database?

(3) One separate table space for all database single table space for storing the indexes.

(4) Is any schema\user security associate with indexes while storing in table space.

Thanks
Reply With Quote
  #2 (permalink)  
Old 11-23-11, 06:35
Marcus_A Marcus_A is offline
Registered User
 
Join Date: May 2003
Location: USA
Posts: 5,198
Generally, indexes should be stored in separate tablespaces so that they can be placed in a separate bufferpool from the data. This is based on the assumption that you may want to have a higher bufferpool hit ratio for indexes than for the data, and that the entire database (tables and indexes) is larger than the amount of bufferpool memory that can be allocated on that server.

The number of tablespaces for data and indexes depends on the size of the database and each table (and whether you will need to do tablespace level backup/restores). Also, having more than one tablespace can improve backup and restore performance in most cases, if the database is large enough.

The above information is for DB2 LUW. DB2 for z/OS has different considerations.
__________________
M. A. Feldman
IBM Certified DBA on DB2 for Linux, UNIX, and Windows
IBM Certified DBA on DB2 for z/OS and OS/390
Reply With Quote
  #3 (permalink)  
Old 11-23-11, 06:42
db2champ db2champ is offline
Registered User
 
Join Date: Jul 2011
Posts: 46
Quote:
Originally Posted by Marcus_A View Post
Generally, indexes should be stored in separate tablespaces so that they can be placed in a separate bufferpool from the data. This is based on the assumption that you may want to have a higher bufferpool hit ratio for indexes than for the data, and that the entire database (tables and indexes) is larger than the amount of bufferpool memory that can be allocated on that server.

The number of tablespaces for data and indexes depends on the size of the database and each table (and whether you will need to do tablespace level backup/restores). Also, having more than one tablespace can improve backup and restore performance in most cases, if the database is large enough.

The above information is for DB2 LUW. DB2 for z/OS has different considerations.
Is any schema\user security associate with indexes while storing in table space.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On