Something probably held a transaction open for a long time, which caused
the transaction log to grow.
Unfortunately, once the file is large, it doesn't get small again, even
if we don't need the space.
On 2012-02-08 16:28, Peter Dahm wrote:
Hi,
we have a problem with the size of our database file.
We have a database file which has a size of 4.2 Gigabyte, but there
are not very much records inside.
May be all together up to 20 tables with 2000 datasets. Some of them
are blobs.
If we dump the database file to sql script and import the data to a
new database the size of the new database file is less than 300 MB.
What might be the reason for the large file ?
What can we do to fix this behaviour ?
Peter
--
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.
--
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.
