<html>
<body>
At 01:10 PM 9/11/2015 -0400, Mark Tompsett wrote:<br>
<blockquote type=cite class=cite cite>Greetings,<br>
> <br>
I would suggest the
<a href="http://cleanup_database.pl">cleanup_database.pl</a> script in
the cronjobs directory, except I've just looked at it and it doesn't
touch the import_items or import_biblios tables.<br>
<br>
As Galen mentioned it does via cascades. Thanks for pointing me at the
better way.</blockquote><br>
+1 (at least for Z39.50.) However for "cleaning up" purposes on
a limited VM machine, what's the size of your inno file? On my sandbox
(perhaps a tad smaller than your example):<br><br>
root@[my_sandbox]:/var/lib/mysql# ls -l<br>
total 1282100<br>
-rw-rw---- 1 mysql mysql 1302331392 Sep 11 17:45 ibdata1<br><br>
which is significant (nearly 4x the clean [1] sql dump at 354330649.) (To
get rid of it in production, you have to delete all MySQL tables before
removing this overweight monstrosity, then restore your dumps - takes
only a few seconds on a fast machine, so I've set up the cron for
"idle hours". Note this is a MySQL problem, not Koha; there was
some talk that MySQL 5.6 would alleviate it, but my experience is that it
does not -- only partiallytested, we're still using 5.5.44 in
production.)<br><br>
Best -- Paul<br><br>
[1] I have things set up to run:<br><br>
./bin/cronjobs/cleanup_database.pl --import 1 &&<br>
./bin/cronjobs/cleanup_database.pl --mail &&<br>
./bin/cronjobs/cleanup_database.pl --sessions &&<br>
./bin/cronjobs/cleanup_database.pl --logs 10 &&<br>
./bin/cronjobs/cleanup_database.pl --zebraqueue 1<br><br>
before mysqldump --user=[munged] --password=[munged] >
[munged]/backup/kohadump_{date}.sql<br><br>
<br><br>
<br>
</body>
</html>