On 2013-09-06 20:15, Brian Craft wrote:
I need to load about 1G of data into an existing db, while maintaining
data coherence. Wrapping the inserts in one transaction results in
out-of-memory problems in the jvm. I increased the max heap size to 8g
w/o improvement. I can split it into a bunch of smaller commits, which
works fine, but then on error I need a bunch of application code to
delete the transactions which succeeded. The deletes will need their
own transactions, which could also fail.
Is there any better way to do this?
Not really.
One strategy would be to copy the DB, since with H2 it's just a single
file, and then run your import process.
If it fails, just replace the modified DB with the backup.
--
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 http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.
