Hi, > We have a situation where we perform some major pruning of a database > (dropping tables, removing columns, deleting a large percentage of the > rows) before closing the database a burning it onto a CD.
I suggest to create a SQL script using "SCRIPT TO", and then recreate the database from that script. Like that the database file size might shrink, and probably the database is a bit faster, because rows for the same table will be next to each other. Additionally, this should also solve the problem you describe. > Very infrequently we run into a situation where when we try to open > the database from the CD it throws an exception and won't open because > it thinks that it needs to recreate some indexes and/or reconcile the > log. That's strange. It's quite hard to say what's wrong... What you could do is: append ;TRACE_LEVEL_FILE=3 to the database URL and send me the .trace.db file if this happens, together with the database. > I am not at all confident that we are shutting the database down > cleanly. Closing all connections should be enough. > Is there any way to wait and check with the database to make sure that > it is completely closed? You could run the SHUTDOWN SQL statement. 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 -~----------~----~----~----~------~----~------~--~---
