Hi, > From what I understand, a non-clustered index will store a key-value > mapping outside of the database where the keys are ordered and the > values are locations of records. A clustered index will actually > store records in sorted order within the database itself, or so I > think.
There is a feature like that on the roadmap, "Index organized tables CREATE TABLE...(...) ORGANIZATION INDEX (store in data file)". Like you wrote, it should improve performance if you access the table using this index (the 'clustered index'). Unfortunately to implement it, a file format change is required. For some cases it will actually decrease performance however, even when accessing the table using this index (for example COUNT(*), MIN(column), MAX(column) with a where clause on the column), so I'm not sure how much it will help in your case. > Hopefully I'm asking a reasonable question. Sure! There are other ways to improve performance. Did you already try out some other options? How much do you need to improve the speed, do you have a specific performance goal? Regards, Thomas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/h2-database?hl=en -~----------~----~----~----~------~----~------~--~---
