It's a MS Access issue where many changes lead to an inefficient database. Regular compacting should help speed things up.

I don't know how this works in MediaMonkey 3 with SQLite as it's file database that get's loaded in instead of a database on it's own (as far as I understand).

My understanding is thus:

as records/data is changed/removed, the database becomes larger but never gets smaller...

compacting the database is akin to defragmenting a hardrive;

- a new database file is regenerated without the empty spaces of old removed data, thus reducing the space
- indexes/tables rebuilt and/or verified for consistency etc
- probly other stuff I forgot or don't know

I have been using MM for a couple of years now, and it is an unsurpassed product in my opinion. But I have never been sure exactly what compacting the database entails - what is actually taking place when the database gets compacted? How does the database gradually get de-compacted? And how often should I do the compacting?

Many thanks.