Re: Tables per Tablespace

For performance reasons, using multiple tablespaces is useful for disk sripping. The aim is to distribute read/write workload between different physical disks. For example, it could be useful to put on two separate disks (datafiles - tablespaces) tables that are frequently read at the same time.

And the decision is to be made at database level : u should take into account other applications having data in the same database - or other databases on the same server (node).

Achille Carette
Bluegate Group
http://www.bluegate.be

<bcarignan_at_my-deja.com> wrote in message news:90o87h$ehg$1_at_nnrp1.deja.com...
> Is there a standard for determining the number of tables that should
> exist in a tablespace? If I can fit all of the tables for an
> application in a single tablespace, which is composed of a single
> datafile are there any performance ramifications? Other than the case
> of very large (>1 GB) tables, when would it make sense to separate
> tables that logically belong together into separate tablespaces?
>
> Brian
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Thu Dec 07 2000 - 09:37:21 CST