Hello, Craig. I come from a DB2 school of training, but am working with Oracle now. We are in the process of adding applications to an Oracle instance, that primarily had only one dominant tablespace. My senior Oracle DBA insists on putting new tables (of the new applications) into the same tablespace.
I some how am allergic to the thought.
I would like to see at least the new tables grouped together in a different tablespace. The performance, recovery and availability issues are almost similar. What are your thoughts?
QUESTION POSED ON: 09 FEB 2005
QUESTION ANSWERED BY: Craig Mullins, Years 2005-2006
Well, Oracle is a different beast than DB2. Interestingly enough, there was a question last week about just the opposite of this one! Read the answer to that question because it will help as you think through your situation.
I don't think it would be problematic to group the new tables and indexes into a different tablespace, though. As soon as you want to treat the new application data differently than the old, it may be easier if they are in a different tablespace. But there is no need to do what you do in DB2; that is, Oracle does not benefit from a one table per tablespace strategy the way DB2 does.
|
|
|
