2005/9/22, Christoph Weser <[EMAIL PROTECTED]>: > Hello Everyone! > > I know this question is quite general, anyway: > > Let's say I have a table for an authorization management. There a table > "user" containing all information about users like name, ID, language and so > on. > In "my real world" there are 100, maybe 200 different users a lot, which > means 100 (or 200) rows in this table. > > So the question: Would it be a good idea to "waste" some space for indices > in this case or will do the database anyway a table scan? Is there a way how > I can estimate if a index is woth the space or not?
AFAIK every table is stored in an index structure (like SQL Server tables with a clustered index). So in this case it seems most efficient to actually define the primary key on user id. see the online documentation: http://dev.mysql.com/doc/maxdb/en/0a/4f379438e5d441b37e5202f35310e4/content.htm Kind regards robert -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
