@SunilKarde1 - the best practice is to separate tables and indexes to reduce fragmentation and contention and to improve performance. I do not recommend placing tables and indexes on the same tablespace. You will need to rebuild indexes often as your data changes overtime (inserts, updates, deletes), having the indexes in a different tablespace improves performance to rebuild indexes, gather new statistics, reduces contention and fragmentation of the tablespace datafiles. If you want to learn more about this then see the link below, read my database guide book for Oracle, the Production Mapping is generic and can be applied to any industry. You can also find there my database template scripts with detail on how to setup the Oracle Enterprise Geodatabase for production.
Mapping and Charting Solutions (MCS) Enterprise Databases Best Practices
I hope this clarifies your question.
| Marcelo Marques | Esri Principal Product Engineer | Cloud & Database Administrator | OCP - Oracle Certified Professional | "In 1992, I embarked on my journey with Esri Technology, and since 1997, I have been working with ArcSDE Geodatabases, right from its initial release. Over the past 32 years, my passion for GIS has only grown stronger." | “ I do not fear computers. I fear the lack of them." Isaac Isimov |
