MediaMonkey uses the SQLite database to store information. The SQLite database is 

by default configured to be very safe even in cases of software or hardware failure. 

However, some users might prefer to sacrifice a little safety and get slightly improved

performance.



For such users, the line indicated below should be added to the [System] section of 

the MediaMonkey.ini file:



[System]

SQLiteSafety=x





Possible values for x are 0, 1 or 2:

 0: fastest-least robust, also known as synchronous = OFF. 

    SQLite continues without pausing as soon as it has handed data off

    to the operating system. If MediaMonkey crashes, the data will be

    safe, but the database might become corrupted if the operating system

    crashes or the computer loses power before that data has been written

    to the disk surface. On the other hand, some operations are as much as

    50 or more times faster at this setting.

 1: medium-very robust, also known as synchronous=NORMAL. The SQLite

    database engine will still pause at the most critical moments. There is a

    very small (though non-zero) chance that a power failure at just the

    wrong time could corrupt the database. But in practice, you are more

    likely to suffer a catastrophic disk failure or some other unrecoverable

    hardware fault.

 2: slow-extremely robust (default), also known as synchronous=FULL. With a value

    of 2, the SQLite database engine will pause at critical moments to make

    sure that data has actually been written to the disk surface before

    continuing. This ensures that if the operating system crashes or if there

    is a power failure, the database will be uncorrupted after rebooting.

    This mode is very safe, but it is also slow.



For more information on editing the MediaMonkey.ini file, see:

http://www.mediamonkey.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=17