> --- Ursprüngliche Nachricht --- > Von: "Hahn, Uwe" <[EMAIL PROTECTED]> > An: "Robert" <[EMAIL PROTECTED]>, "MaxDB" <maxdb@lists.mysql.com> > Betreff: RE: Clarification: Table and Index Storage > Datum: Tue, 24 May 2005 13:22:01 +0200 > > >-----Original Message----- > >From: Robert [mailto:[EMAIL PROTECTED] > >Sent: Tuesday, May 24, 2005 1:14 PM > >To: MaxDB > >Subject: Clarification: Table and Index Storage > > > > > >Hi folks, > > > >just wanted to check that my understanding of MaxDB internals > >is correct: > > > >Each table has a primary key (user provided or generated by > >the DBMS). So > >each table is stored as a B*TREE, i.e. the leaf pages of the PK contain > >the rows (as opposed to Oracle for example where this is only > >the case for > >tables with option INDEX ORGANIZED; MS SQL Server stores the table as > >B*TREE as soon as there is a CLUSTERED (= ordered) index on a table). > > > >Is this correct? > > Yes. > > > > >Additional question: how does MaxDB generate the primary key > >if the user > >does not provide one? Does it use some kind of rowid for > >this? Is there > >a storage space overhead associated with this (because of an additional > >field)? > > > > If no primary key is defined a unique number for this table is generated > which has a size of 8 bytes.
Then there is actually a space overhead of 8 bytes per record. Good to know. Thanks a lot for the info! Kind regards robert -- Weitersagen: GMX DSL-Flatrates mit Tempo-Garantie! Ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
