| Single big tablespace versus multiple tablespace [message #490714] |
Wed, 26 January 2011 22:47  |
shrinika
Messages: 306
Registered: April 2008
|
Senior Member |
|
|
My database version is
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
PL/SQL Release 11.1.0.7.0 - Production
CORE 11.1.0.7.0 Production
TNS for Linux: Version 11.1.0.7.0 - Production
NLSRTL Version 11.1.0.7.0 - Production
My os version is
Linux damdat01 2.6.18-128.7.1.el5 #1 SMP Wed
Aug 19 04:00:49 EDT 2009 x86_64 x86_64 x86_64
GNU/Linux
My database is OLP system.
My question is what are the advantages and disadvantages
having one single tablespace versus multiple tablespace?
Easy to maintain when you have single tablespace.
but hard to track the IO issues if you have
one single tablespace.
Any other input from any one? Please let me know.
[Updated on: Wed, 26 January 2011 22:49] Report message to a moderator |
|
|
|
|
|
|
|
|
|
|
|
| Re: Single big tablespace versus multiple tablespace [message #490774 is a reply to message #490714] |
Thu, 27 January 2011 05:07  |
 |
Mahesh Rajendran
Messages: 10707
Registered: March 2002
Location: oracleDocoVille
|
Senior Member
Account Moderator |
|
|
Has nothing to do with I/O.
Just provides some flexibility.
You can backup individual tablespaces, export tables in specific tablespaces and all.
By meaning a single large tablespace are you implying single large data file too? That could be a different story.
In previous versions, RMAN cannot do a multisection backup, which was little inconvenient.
[Updated on: Fri, 28 January 2011 13:59] Report message to a moderator |
|
|
|
|
|
| Re: Single big tablespace versus multiple tablespace [message #492316 is a reply to message #491061] |
Sat, 29 January 2011 06:03 |
John Watson
Messages: 8931
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
You might want to think about transportable tablespaces (will you ever need to copy a limited set of objects from one database to another?) and read only tablespaces (can you isolate a set of objects that will not be updated from the others?) and mirroring with RAID or ASM (would you want different levels of protection for different tablespaces?) and transparent tablespace encryption (can you group objects that must be encrypted together?)
One huge tablespace? Not many options there.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
