Depends: how many tweets did you store? I would be more concerned in case you store blobs in the db, which to me is inefficient regardless of the db engine.
On Tuesday, May 9, 2017 at 12:57:23 PM UTC+2, [email protected] wrote: > > I didn't look at Scriptella. fetch size = 10000 doesn't improve anything. > Now I'm copying the rows based on their id, using "where id > ... and id < > ...", which works. > > I suppose h2 isn't made for large data sets. > > Am Montag, 8. Mai 2017 16:50:03 UTC+2 schrieb Christian MICHON: >> >> Did you have a look at Scriptella? >> >> I suggest to pay attention to fetch size and batch size as jdbc >> parameters. >> >> You might want also to export to another h2 first to see if any potential >> issues with index sizes or data corruption. >> >> -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
