By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,502 Members | 1,878 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,502 IT Pros & Developers. It's quick & easy.

how many tablespaces

P: n/a
Hi ,

We will have about 50 tables. Some tables will be huge (severel
million rows) and some are small but most of them will have about a
million rows. For best performance of the database, how many
tablespace should I have. I was thinking of using Locally Managed
tablespaces (uniform extents) for both data and indexes.

Can anyone share some experiences? Any other tips on layout of the
database will be appreciated. Thanks

Vissu
Jul 19 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a

"Vissu" <vi*****@yahoo.com> wrote in message
news:2b**************************@posting.google.c om...
Hi ,

We will have about 50 tables. Some tables will be huge (severel
million rows) and some are small but most of them will have about a
million rows. For best performance of the database, how many
tablespace should I have. I was thinking of using Locally Managed
tablespaces (uniform extents) for both data and indexes.

Can anyone share some experiences? Any other tips on layout of the
database will be appreciated. Thanks

Vissu

What version? Use locally managed with auto managed extents and put the
data all in one tablespace.
Jim
Jul 19 '05 #2

P: n/a
"Jim Kennedy" <ke****************************@attbi.net> wrote in message news:<Tly1c.112729$4o.138921@attbi_s52>...
"Vissu" <vi*****@yahoo.com> wrote in message
news:2b**************************@posting.google.c om...
Hi ,

We will have about 50 tables. Some tables will be huge (severel
million rows) and some are small but most of them will have about a
million rows. For best performance of the database, how many
tablespace should I have. I was thinking of using Locally Managed
tablespaces (uniform extents) for both data and indexes.

Can anyone share some experiences? Any other tips on layout of the
database will be appreciated. Thanks

Vissu

What version? Use locally managed with auto managed extents and put the
data all in one tablespace.
Jim


How many tablespaces you should use to support your database depends
on the expected size and number of your objects and the organization
of your disk farm.

I greatly favor organizing most applications into large and small
object tablespaces. Generally two sizes will work for everything.
The best sizes depend on the objects involved.

I do not like autoallocate because it still can suffer from the free
space fragmentation problem while a properly sized uniform extent
tablespace will never suffer this problem. The only time I think
autoallocate is useful is where you install a canned package and the
vendor places everything into a single tablespace (usually the
application owner default tablespace).

It all comes down to judgment on which arrangement will provide the
most effective managment options.

IMHO -- Mark D Powell --
Jul 19 '05 #3

P: n/a

"Mark D Powell" <Ma*********@eds.com> wrote in message
news:26**************************@posting.google.c om...
| "Jim Kennedy" <ke****************************@attbi.net> wrote in message
news:<Tly1c.112729$4o.138921@attbi_s52>...
| > "Vissu" <vi*****@yahoo.com> wrote in message
| > news:2b**************************@posting.google.c om...
| > > Hi ,
| > >
| > > We will have about 50 tables. Some tables will be huge (severel
| > > million rows) and some are small but most of them will have about a
| > > million rows. For best performance of the database, how many
| > > tablespace should I have. I was thinking of using Locally Managed
| > > tablespaces (uniform extents) for both data and indexes.
| > >
| > > Can anyone share some experiences? Any other tips on layout of the
| > > database will be appreciated. Thanks
| > >
| > > Vissu
| > What version? Use locally managed with auto managed extents and put the
| > data all in one tablespace.
| > Jim
|
| How many tablespaces you should use to support your database depends
| on the expected size and number of your objects and the organization
| of your disk farm.
|
| I greatly favor organizing most applications into large and small
| object tablespaces. Generally two sizes will work for everything.
| The best sizes depend on the objects involved.
|
| I do not like autoallocate because it still can suffer from the free
| space fragmentation problem while a properly sized uniform extent
| tablespace will never suffer this problem. The only time I think
| autoallocate is useful is where you install a canned package and the
| vendor places everything into a single tablespace (usually the
| application owner default tablespace).
|
| It all comes down to judgment on which arrangement will provide the
| most effective managment options.
|
| IMHO -- Mark D Powell --

also should take into consideration grouping segments for similar
availability / back-up schedules / transportability / read-only and similar
tablespace-specific operations

;-{ mcs
Jul 19 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.