Hi, The database probably doesn't re-use empty space immediately at the moment (I do plan to change that), so if you run RUNSCRIPT to replace the data, the old space is not recovered. So to shrink a database, you need to run RUNSCRIPT against an empty database. As far as I understand, this works for you?
Regards, Thomas On Tue, Jun 9, 2009 at 12:29 AM, PatMac<[email protected]> wrote: > > Hello, > > The data.db file is 160 (was 96) > The index.db is 96 and was 96 before the recover tool. > There are log.txt (3.6 mb) and index.txt (3 mb). > There is a log.db 392 kb. > > So apart from the txt files that are new and I guess can be deleted, > there is only the data.db file that has grown what seems to be too > much. The database is working ok. > > Thanks > > Patrice > > > On 8 juin, 13:16, Thomas Mueller <[email protected]> wrote: >> Hi, >> >> > The file went from 96 to 160 mb (when I runscript to restore from the sql >> > file). >> >> Which file, the .data.db file? Could you post the complete list of >> files with the file sizes before and afterwards? >> >> 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 -~----------~----~----~----~------~----~------~--~---
