The HSQLDB user guide for version 1.8 (which is what is used in all
LO versions) is available at:
down to section 5.2. It should be answer your questions. The AutoRecovery
is found: Tools > Options > Load/Save > General. Look in the Save section
for settings for backups and AutoRecovery. I have not used MS Word since I
used Win 98SE in the 90's so I do not know. (I have used Linux for more
than ten years.)
CHECKPOINT DEFRAG might be a good command to use to reduce the size
of the database. Another command that you could use when you finish working
with Base: SHUTDOWN COMPACT. The user guide explains what this will do. But
only use it when you are ready to close Base. Then use Tools > SQL and
enter SHUTDOWN COMPACT; in the Command to execute box. The semi-colon is
required at the end of the command. After executing this command
successfully, close Base. If your database is somewhat bloated, this will
reduce its size.
I found this in an email I received earlier, perhaps from this
- hsqldb embedded databases will now systematically be subjected to a
"checkpoint" and/or "checkpoint defrag" on saving of the database file. The
aim with this change is to force hsqldb to optimize the size of the db,
especially where frequent deletions of data sets are carried out. With a
bit of luck, it might actually bring long-term benefits like increased data
security and stability (he says, crossing fingers). There may well be a
performance hit when closing the ODB file, especially on big databases, but
the developer who implemented this change feels that people who want to
manipulate large datasets should be using something a bit more appropriate
than an embedded hsqldb...
The date on the above email was a couple of weeks ago. So, this
statement likely does not apply to LO 188.8.131.52.
On 01/20/2013 10:04 PM, Hank Alper wrote:
Thanks for your quick response. I"m using LO version184.108.40.206 Build ID
:2ef5aff on a Windows 7 Pro machine. My machine's processor is an Intel
i7-2600K with 8Gig of memory and 1TB hard drive. I use periodic backups to
another machine on my network. As for AutoRecovery, whenever there is a
catastrophic failure Base auitomatically tries to recover my database file
on the next start-up. Is that what you're referring to.? If not, I was
unaware that Base has such a feature.Is it similar to that used In MS Word?
As for CHECKPOINT, I have not used that SQL command. When would it be
appropriate to use it? As for CHECKPOINT DEFRAG, when should that be used.
That might be useful as Base is getting much less responsive, seems
bloated.. The size of my database file is about 360 KB.
On Sun, Jan 20, 2013 at 4:55 PM, Dan Lewis <email@example.com>wrote:
On 01/20/2013 04:31 PM, Hank Alper wrote:
I've invested a considerable amount of time in constructing tables, forms
and queries for a project of mine. I successfully produced 3 nice reports
using Report Builder. Now, I'm starting to observe strange behavior in
Base. Queries and Reports I've prepared days earlier suddenly disappear
after I've used them in Report Builder to prepare or edit a Report. As an
example, I've just used Report Builder to design a report, saved my work
and closed the file. I then ran the report in the viewer and it was fine,
but needed minor tweaking.I closed the viewer and then right clicked on
icon for my report in order to continue editing. LO closed down! When I
restarted, LO blithely announced it was recovering my database. It did,
the new Report and the modifications to a query I made in this session
gone. I think* most* of this behavior is due to Report Builder. Has
else observed this type of behavior before ?.
We need some basic information. What version of LibreOffice are you
using? What operating system do you use? Do you use backups or
AutoRecovery? Have you ever used CHECKPOINT as a SOL command? It closes the
database files, rewrites the script file, deletes the log file and opens
the database. If CHECKPOINT DEFRAG is specified, this command also shrinks
the .data file to its minimal size.