Hmm, Thomas, you wrote earlier
> Could you explain what you need and why? I guess my answer really didn't explain why I need clustered index support. My records/rows contain a timestamp attribute, and they will be inserted into the database in chronological order. The queries will have a time range component to searches, so it would be best for reading if my records were sorted by time. My understanding is that a clustered index also benefits because there are fewer page faults since the index is "in" the database since the rows are sorted by on that timestamp (key) attribute. I currently have a query resembling "CREATE INDEX ON TABLE(timeAttribute)." It does not seem like this doing the job because inserts are getting slower as the database grows. Clustered indices allow inserts and reads to be fast if the records are inserted in sorted order. That ought to be a better explanation of what I'm trying to do. Maybe there's a better alternative to my implementation. -Julian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
