Широко разпространено е убеждението, че поддържането на индекси и таблици в отделни таблични пространства подобрява производителността. Сега това се смята за мит от много уважавани експерти (вижте тази тема на Попитайте Том - потърсете "мит" ), но все още е обичайна практика, защото старите навици умират трудно!
Редактиране от трета страна
Извлечение от asktom:„Индексиране на таблично пространство“ от 2001 г. за Oracle версия 8.1.6 въпросът
- Все още ли е добра идея индексите да се държат в тяхното собствено таблично пространство?
- Това подобрява ли производителността или е по-скоро проблем с възстановяването?
- Отговорът различава ли се от една платформа до друга?
Първа част на отговора
Yes, no, maybe.
The idea, born in the 1980s when systems were tiny and user counts were in the single
digits, was that you separated indexes from data into separate tablespaces on different
disks.
In that fashion, you positioned the head of the disk in the index tablespace and the head
of the disk in the data tablespace and that would be better then seeking 2 times on the
same disk.
Drives back then were really slow at seeking and typically measured in the 10's to 100's
of megabytes (if you were lucky)
Today, with logical volumes, raid, NN gigabyte (nn is rapidly becoming NNN gigabytes)
drives, hundreds/thousands of concurrent users, thousands of tables, 10's of thousands of
indexes - this sort of "optimization" is sort of impossible.
What you strive for today is to be able to manage things, to spread IO out evenly
avoiding hot spots.
Since I believe all things should be in locally managed tablespaces with UNIFORM extent
sizes, I would say that yes, indexes would be in a different tablespace from the data but
only because they are a different SIZE then the data. My table with 50 columns and an
average row size of 4k might belong in a tablespace that has 5meg extents whereas the
index on a single number column might belong in a tablespace with 512k or 1m extents.
I tend to keep my indexes separate from the data but for the above sizing reason. The
tablespaces frequently end up on the same exact mount points. You strive for even io
across your disks and you may end up with indexes and data on the same devices.
