There are actually several very good reasons to separate them. The first and most important is recovery. If you lose an tablespace with only indexes, you can always re-create the indexes. If you lose a tablespace with both, you have a recovery involved. The next is manageability. Its just easier to manage things if you keep tables and indexes separate. The third reason is you may not know or have control of the underlying storage, but you should have control of the tablespace layouts. > > > http://richardfoote.wordpress.com/2008/04/16/separate-indexes-from-tables-some-thoughts-part-i-everything-in-its-right-place/ > > http://richardfoote.wordpress.com/2008/04/18/separate-indexes-from-tables-some-thoughts-part-ii-there-there/ > > http://richardfoote.wordpress.com/2008/04/23/separate-indexes-from-tables-some-thoughts-part-15-think-for-yourself/ > > http://richardfoote.wordpress.com/2008/04/28/indexes-in-their-own-tablespace-availabilty-advantages-is-there-anybody-out-there/ > > http://richardfoote.wordpress.com/2008/05/02/indexes-in-their-own-tablespace-recoverability-advantages-get-back/ > > It covers pretty much everything you need to know about this index/data > tablespace(s) story.. > > > ciao. > > -- > Nilo Segura > Oracle Support - IT/DES > CERN - Geneva > Switzerland -- Andrew W. Kerber 'If at first you dont succeed, dont take up skydiving.'
