An embedded database storage engine with 100 million rows? That's ... bigger than what I would think is the sweet spot for an embedded db.
Either way, I would look into changing the page size and the cache size; both can be specified in the connection url, I think, and the page size can't be changed after the db is created. Chris On Thu, Jun 23, 2011 at 2:53 AM, Stephane Geney <[email protected]> wrote: > Hi, > > I've just started using H2 for my application as an embedded database > storage engine and it's really working great except for one part : > > I have a table with 3 columns : id1 char(8), id2 char(8), value float. > I need indexes on the first two columns separately as I'll do a lot of > (select..where id1=...) and (select... where id2=...). > > The table as more than 100 millions rows, and the index creation is > just too long. Creation of index on column id2 took more than 10 > hours. > > Is there a workaround ? should I try to create the indexes first and > then only import data in the table by splitting in in smaller chunks ? > > Thank you for your answers. > > -- > 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. > > -- C. Schanck -- 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.
