Multiple tables or single table in one tablespace ?

Hi , all
We have hundreds of tables in on tablespace ,
but I'm planning to change as one table per one tablespace. .

I wonder how other shops does ?

Are there any special reasons in UDB
keeping multiple tables in one tablesapce ?


Regards
Myoungsoo

Ex M/F DBA

Hi!

We group tables in tablespace by logical groups. For example, all common
tables (like currency, country, ...) are in one tablespace. If we have
large tables that need to be fast we usually use range partitioning
across multiple tablespaces.

Best regards,
Kovi

mvsmsh pravi:
> Hi , all
> We have hundreds of tables in on tablespace ,
> but I'm planning to change as one table per one tablespace. .
>
> I wonder how other shops does ?
>
> Are there any special reasons in UDB
> keeping multiple tables in one tablesapce ?
>
>
> Regards
> Myoungsoo
>
> Ex M/F DBA

--
____________________________
|http://kovica.blogspot.com|
-----------------------------~-~-~-~-~-~-~-~-~-~-
| In A World Without Fences Who Needs Gates? |
| Experience Linux. |
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-

mvsmsh wrote:
> Hi , all
> We have hundreds of tables in on tablespace ,
> but I'm planning to change as one table per one tablespace. .
>
> I wonder how other shops does ?
>
> Are there any special reasons in UDB
> keeping multiple tables in one tablesapce ?
With automatic storage the administrative overhead to a tablespace is
minimal. The benefit of a table space however is that it can be restored
individually.
So having each table in a separate tablespace provides essentially table
level backup/restore.
I think there are also some locks that are table space level.
Overall best practices are moving towards one table per tablespace.
If that is becoming pervasive the question: Why does DB2 distinguish
between table spaces and tables to begin with" is quite fair.

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab