Seema - My interpretation of your question is that you are asking whether
having the indexes for a table on a separate physical would increase
performance.
Since this was a standard recommendation for many years, I feel it merits a
more detailed reply.
If you have an OLTP benchmarking
Title: RE: Index move
There is no logic which says index on different
disk can give better performance . Instead spreading tables and indexes across
disks based on application can help in performance .
bp
- Original Message -
From:
Anjo Kolk
To: Multiple recipients
Title: RE: Index move
Seema,
The big question: where is the table? Forgetting about RAID, having the index on a different disk from the table should give you better performance.
As far as moving the index to another tablespace without considering the table, it depends on what else
Title: RE: Index move
"having the index on a different disk
from the table should give you better performance."
Why ?
- Original Message -
From:
Whittle Jerome Contr NCI
To: Multiple recipients of list ORACLE-L
Sent: Monday, August 19, 2002 7:24
PM
S
Unlikely.
If you can a balanced load across the disks you have
available where balanced means evenly spread across:
- short peak volume timescales
- longer summary timescales
then you'll be pretty close to optimal. That does not
necessarily mean separating data from indexes
hth
connor
Title: RE: Index move
Go get 'em, big guy!
- Original Message -
From:
Anjo Kolk
To: Multiple recipients of list ORACLE-L
Sent: Monday, August 19, 2002 11:43
AM
Subject: Re: Index move
"having the index on a different
disk from the table should giv
Title: RE: Index move
I always want to learn :-)
- Original Message -
From:
Tim Gorman
To: Multiple recipients of list ORACLE-L
Sent: Monday, August 19, 2002 8:28
PM
Subject: Re: Index move
Go get 'em, big guy!
- Original Message -
From
If your index tablespace is on the same physical
device than your table tablespace , you will have no
gain.
Is your bottleneck an IO one ?
--- Seema Singh [EMAIL PROTECTED] a écrit :
Hi
I have few of primary key and unique indexes on
main data tablespace.I am
thinking that if I moved
1. Data and Index segments have different storage and sizing requirements.
That's the main reason for them to be put up in different tablespaces.
2. If all indexes are in a seperate tablespace of their own, one could
avoid backing up this tablespace if time and space are a constraint.
3. The I/O
In a multi-user system, you do not get any performance gain by separating indexes from
their associated tables. However I like to place them in different tablespaces for
other reasons: tables and their corresponding indexes grow at different rates and I
prefer to have objects of different
What about spooling the following output to a file and running it?
SELECT 'ALTER INDEX '||index_name||' REBUILD TABLESPACE new tablespace'
FROM dba_indexes
WHERE tablespace_name='current tablespace'
--
Chris J. Guidry P.Eng.
ATCO Electric, Metering Services
Phone: (780) 420-4142
Fax: (780)
How about:
set pages 0
set termout off
set feedback off
spool temp.sql
select 'alter index '||owner||'.'||index_name||' rebuild tablespace '
||tablespace_name||'_idx;'
from dba_indexes
spool off
Ana E. Choto
Systems Programmer
American University
e-Operations
Phone (202) 885-2275
Fax
12 matches
Mail list logo