A Design Issue

Qs What should be the Spirit behind Grouping Tables of a Product into Tablespaces .

PARTICULARS -
- Banking Application Product - Thus a Both OLTP & Batch processing
Occur
- Large Data Size , Existing Database Sizes = 500GB to 1TB

• Total 425 Tables
• Large percent of Tables Undergo DMLs
• A Few History Tables Exist
• Generally 1 Transaction does NOT touch more than 5 Tables .

Qs Should Only the Size of Data in Tables Govern their Distribution into Tablespaces ?
Qs Does the Nature of Operation ( SELECT , INSERT , DELETE , UPDATE ) influence the
Grouping of Tables into Tablespaces ?
Qs Any Best Practices , Documents / Links ?   

NOTE Of now 425 Tables Exist in 41 Tablespaces

Will provide any other info required

--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: VIVEK_SHARMA
  INET: VIVEK_SHARMA_at_infy.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).