I ran "Optimize database (Complete)" and the DB size went from 140MB to 63MB for 18k files / 338GB. Took less than a minute. Not bad at all.

You can do database maintenance by going to File > Maintain Library > Optimize Database.

I too have noticed lastplayed/count missing in some tracks and vids. I have never found a reason/symptom. It is not consistent enough to run a log or anything else. It just happens

Peke wrote:

dypsis wrote:And play dates are getting messed up.

Can you clarify that?

Many examples. Try this one...

I am playing The Beatles (Stereo Remaster) which I have been playing since 2009, and MediaMonkey play count for ALL tracks is 0.

Lowlander wrote:If you play files from My Computer it won't track Play History, it will show during the session, but that's it. Files need to be in the Library to have their Play History saved over sessions.

Yes, I know.

If you play files from My Computer it won't track Play History, it will show during the session, but that's it. Files need to be in the Library to have their Play History saved over sessions.

Example: Sometimes if I played an album yesterday or a couple of days ago, and then I open up MM today, those play dates are not there anymore and only display dates of some time further in the past.

dypsis wrote:And play dates are getting messed up.

Can you clarify that?

And play dates are getting messed up.

I am not concerned about the size of the database.
I just thought that I may have noticed a difference.

But, I am concerned of ensuring that it stays healthy.

The general idea of Optimization is to fix little inconsistencies that bog the database down from running smoothly.
Sure, it might compact it/reduce size some after also deleting empty space characters. But I don't think we're talking
differences of, say, from 122mb to 112mb or even 122mb to 117mb for most people (you might get those numbers
if you optimize (complete) after a few years of "frequently" deleting stuff from the database without any maintenance).

Have you or anyone else ever noticed a "significant enough" difference in size to matter much (size wise,
not overall database health) after doing an optimization and pre-optimization comparison test?

MMFrLife said: It's not supposed to (that is significant enough to matter).

From here:http://sqlite.org/lang_vacuum.html

"Unless SQLite is running in "auto_vacuum=FULL" mode, when a large amount of data is deleted from the database file it leaves behind empty space, or "free" database pages. This means the database file might be larger than strictly necessary. Running VACUUM to rebuild the database reclaims this space and reduces the size of the database file."

So are you saying that MediaMonkey's complete optimisation does not compact the database?

dypsis wrote:I optimized the database. It didn't make any difference to the size though.

It's not supposed to (that is significant enough to matter).

Yes, you're right.

I optimized the database. It didn't make any difference to the size though.

No surprise really. If you perform a pragma integrity check on an MM database after complete optimisation you'll probably find a load of missing references (that shouldn't be there). MM is the only SQLite database that I have which fails the test.