Ok, so did what you recommended. The thumbnails still not showed up after transferring the database using the Mezzmo tools from the old to the new path. Only Backdrops worked, as before.
It's getting technical now:
So I looked into "Mezzmo.db" with "SQLLite Spy" and found out that, TABLE MGOBackdrop was updated correctly with the correct paths.
On the other hand, TABLE MGOPoster had only updated the last row (highest ID) with the correct paths, all other rows had the old path 
So, I executed the following SQL statement to fix the other rows:
Code:
UPDATE MGOPoster
SET Path = REPLACE(Path, 'E:\Mezzmo Database\', 'I:\Mezzmo\Database\')
WHERE Path LIKE ('E:\Mezzmo Database\%')
This updated only the first around 10k entries, then it stopped with an SQL 19 Error - a UNIQUE Constraint violation of the tables INDEX:
Code:
CREATE UNIQUE INDEX Index_MGOPoster ON MGOPoster (Path);
DROP'ing the INDEX fixed that, but the INDEX could not get created again because of the still violated constraint. Also I don't know how the Mezzmo DB would handle that, my last SQL sessions during my study are to long ago and I don't work on the low end level of databases very often now. So, I restored the backup of the "Mezzmo.db" and did another approach.
I DELETED only the ROW with the one correct path (with the last/highest ID) and executed the SQL statement to fix the paths again and it run through without the error.
Now the Thumbnails seem to work as they should.
So it looks like the Mezzmo tools that change the database paths during your migration process created an inconsistent state of the TABLE MGOPoster, that resulted in this operation getting aborted.
Another question:
I also noticed there is a huge amount of old database entries containing old file paths to files that no longer exist. These are basically files that have been moved from local disks to the NAS, all using the Mezzmo tool to fix the path inside the app after they have been copied to the NAS. That only worked half way, because a lot of files where considered as new when starting the maintenance library process.
Therefore, there is also a huge number of unused images for these files in the ".../Artwork/..."-folder. It’s now almost 25 GB huge and probably only 1/4 of this is still relevant.
Is there a maintenance option in Mezzmo to get rid of all these abandoned data?
Selecting the option "remove files not found during the maintenance process" seems not to remove these old entries and artwork form the DB so its growing over time. No wonder the maintenance process takes days to complete.
Compressing the DB with the Mezzmo Tools did nothing but give me 86 MB less from a normaly 2 GB "Mezzmo.db". Also zero change to the mentioned abandoned database entries and the obsolete thumbnails in the Artwork-folder.
Display of existing video thumbnails broke after backup restore on new system
Reply With Quote
Originally Posted by Peter
Bookmarks