How many tablespaces should I have for user data?
Date: 1995/10/07
Message-ID: <455ugg$opa_at_isis.fiu.edu>#1/1
I have a few questions pertaining to applicatrions and their tablespaces with their corresponding schema objects:
- At the moment I have a USER_DATA tablespace that holds tables for all applications' tables. I would like to create one tablespace for each application and its schema objects (tables, indexes, views, etc.) Also I would like to have one tablespace for common objects related to all applications and one tablespace for developers to test new tables before they are in use by production apps.
1a) Is this how its usually done? 1b) Are there any benefits in doing it this way? 1c) Is data retrieval any faster than having all tables inone user_data tablespace?
2) I read in the docs that fewer large data files is better than having many small data files within a tablespace. I am just wondering is there a standard size to start with? What is a good data file size to start with?
Any suggestions you may have will be appreciated.
Note: We are starting out small, we have a 30 NAMED user license and 10 CONCUR license. This is running on a Windows NT Server that will hold tables for approx 5-10 apps. Plenty of data will be stored on the server from Programming Requests to Inventory of all devices at THE DISTRICT (my place of employment). Each app may have approx 10 dedicated tables with their corresponding indexes and views. Common tables to all apps would start at around 10.
Thanks again,
Eddie Hernandez North Broward Hospital District Programmer/Oracle DBA 1608 SE 3rd Avenue hernb0_at_nbhd.org Ft. Lauderdale, FL 33316Received on Sat Oct 07 1995 - 00:00:00 CET
***************************************************************************