by Friedrich » Sat Feb 19, 2011 4:16 pm
The problem is gone after a complete optimization.
The MM.db was an almost completely "fresh" one from a new installation.
I did not expect the DB to be so far from an optimal/optimized state with almost no interference from my side.
Maybe there is a problem with the standard scan/rescan operations, that lead to such suboptimal initial results?
The problem is gone after a complete optimization.
The MM.db was an almost completely "fresh" one from a new installation.
I did not expect the DB to be so far from an optimal/optimized state with almost no interference from my side.
Maybe there is a problem with the standard scan/rescan operations, that lead to such suboptimal initial results?