Single, Locally Managed system managed tablespace

For the evoloution of our product we are considering moving to a single system managed tablespace. The application is a very straight forward OLTP system, while it has a lot of tables none of them are big (half a million on a couple). There are two notable exceptions to this, where Documents and notes are stored, these (especially the document one) can get very big (but not always). At the moment we are going to go for a single Tablespace but advise that if they plan to hold lots of documents or lots of adhoc notes then they may wish to move these tables to a seperate tablespace.

Can anyone give reasons why this would not be a sensible thing to do? Would you bulk if given this advice when implementing a new OLTP system? Do people still like Data / Index / LOB on seperate TS's for administration reasons?

Thanks in advance,

Mike. Received on Fri Jan 19 2007 - 10:42:15 CST