| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Manty tablepsaces in a small database
You, keep stating that this is a small system. Is it going to stay small?
What are the prospects for growth?
When the users see what great wonders they can do with your system are they
going to want more from it? If you can answer no/none/no to all of these
then one your one mount point and one tablespace (two actually - do separate
indexes) system will probably work OK. However, if it starts to grow
migrating it to a scalable platform requires scalable design at the base
level. You can migrate a system such as you described, but it takes alot
more work than just plugging in another array, setting up an LV and moving
the appropriate datafile(s). Consider this before you lock yourself into a
"only a small system" design.
Rodd Holman
Enterprise Data Systems Engineer
LodgeNet Entertainment Corporation
rodney.holman_at_lodgenet.com
Comments made are my own opinions and views. They do not represent views,
policies, or procedures of LodgeNet Entertainment Corporation
-----Original Message-----
From: Javier Morales [mailto:Javier_at_infojobs.net]
Sent: Monday, October 23, 2000 10:36 AM
To: Multiple recipients of list ORACLE-L
Subject: RE: Manty tablepsaces in a small database
so, maybe you don't need much tablespaces...
... I mean, The reading of a table using a index, if it's separate in another tablespace and you use several mount points, then there can be a increase in the results' speed. That's clear, but if you only have one mount point... who knows!... maybe you need someday to set up free space and you can drop a entire tablespace.
;-)
(a bored dba, too...)
-----Mensaje original-----
De: paquette stephane [mailto:stephane_paquette_at_yahoo.com]
Enviado el: lunes 23 de octubre de 2000 15:01
Para: Multiple recipients of list ORACLE-L
Asunto: Manty tablepsaces in a small database
Hi,
I've been caught in this small database project. My question is do you create many tablespaces to separate tables, indexes, the different repositories stored in the db,... For now, there is more trouble than any gain.
For example, this a dss system with fact and dimension
tables. Usually the fact tables are huge and have
their own tablespaces or each partition has its own
tablespace. This time, I can put everything in 1
tablespace.
Also, since it's small, I do not have many independant
mount points so what is the gain of using many
tablepsaces ?
A bored dba
TIA
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).
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 Received on Mon Oct 23 2000 - 10:07:53 CDT
 |
 |