SMS Table space:
Table is the 11th one, table Bis the 12th
Each table is built as a separate file (sql00011.dat and sql00012.dat)
Since it is SMS then the writing to is outside of DB2 control and under the file
system used.
DB2 will call for the write of the data page and the file system will write it
wherever it feels on the drive. Leads to fragmentation.
DMS table space:
Table A has a preallocated extent (extent size) at the start and so does table
B. Each is unique.
Pages will be written in the proper extent until full and then new extents will
be allocated on demand. So, yes, EXT1 of Table A could be followed by EXT1 and
EXT2 of table B and then EXT2 of table a and so on.
Please note taht for each table DB2 maintains an extent map for each table and
caches that in memory at first access. When doing scans then DB2 knows which
extents to retrieve at which location on the container.
HTH, Pierre.
Daniel Scheibli wrote:
> Hi folks,
>
> today I talked with an Oracle guy and in this
> conversation and interesting question came up:
>
> If we have 2 tables in one tablespace, are
> there any rules how the pages of the tables
> are organized? Are they grouped like AAAABBBB
> or are they written on demand like maybe AABABBAB?
>
> Has anyone the solution or where to find such
> informations?
>
> Thanks in adavanced
>
> Daniel
>
> --
> Daniel Scheibli
> Karlsruhe, Germany
>
> Sent through GMX FreeMail - http://www.gmx.net
>
> =====
> To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
> For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
