Christoph Weser wrote: > Hello everyone. > > I'm using 7.4.3.32 on Windows and have a small question. > > The table is: > > create table s_event ( > EID FIXED(38,0) NOT NULL, > ETID FIXED(38,0) NOT NULL, > SID FIXED(38,0) NOT NULL, > CID FIXED(38,0), > eventtime FIXED(38,0) NOT NULL, > data LONG BYTE > ) > > With folloing indices: > > create index s_event_x1 on s_event(EID) > // > create index s_event_x2 on s_event(ETID) > // > create index s_event_x3 on s_event(SID) > // > create index s_event_x4 on s_event(CID) > // > create index s_event_x5 on s_event(eventtime) > > Now I have populated the table with arount 13.000.000 rows. > EID and eventtime is for each row different, CID is often > null, ETID has > just let's say around 10 different values, the same with SID. > > But when I check the index sizes (select * from INDEXSTATISTICS WHERE > Description = 'Used pages') I see, that the Index s_event_x1 > has around > 56000 pages, all others around 36000 pages. > > Is there an easy explanation whe x1 is that big? > > Tahnx a lot! > > Chris
Hi, simplified in MaxDB an index is a list of primary keys behind the index value. So if one index value hits more primary keys you save space because the index value is only stored once. Kind regards Holger -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
