All forums > ThumbsPlus v7-v9 Questions
Save My database! (making it smaller)
Greatly Perturbed:
My database is hitting the jet 2GB limit. What are my options?
1. Is there a way to convert the database to Sqlite3 format?
2. How to get the thumbnails out of the database and into separate files?
I found the solitary python script in the undernourished Help files, but of course no instructions in how to actually use it. I mean, what's the point of having that search box on the mainscreen when the help files are so meagre? Grrr!
My thumbnail options are currently 96 by 96, 24 bit color, no compression. Please don't suggest changing the format to jpg or using a different color depth. I've tried for several days doing that on copies of the database and it always ends up bigger!
My final goal is to have my thumbnails at 120 by 120 size. I need about 5% wiggle room as this database won't grow very quickly.
I rally hope someone out there can help me. Thanks for reading.
Daan van Rooijen:
> My database is hitting the jet 2GB limit. What are my options?
I'd start by removing any/all orphans and compressing the database.
Orphans: Thumbnail | Remove | Orphans | All Local Disks
Compress: Database | Advanced | Compact & Repair
I'm sorry for raising the taboo subject anyway, but I can't believe that uncompressed thumbnails would take up less space than JPG-compressed thumbnails. How many thumbnails do you have? (see Database | Statistics). With my current thumbnail settings (160x160 pixel, JPG Q88) I can store over 200,000 thumbnails before the database hits 2GB. At only 96x96 pixels, yours should contain some 500,000 thumbnails at that point if you used the same JPG compression (but uncompressed, those 500K thumbnails would consume 96x96x3 x 500,000 + some overhead = ~15 GB harddisk space.. hence my disbelief).
Greatly Perturbed:
Thanks for the reply I did as you suggested and reduced the file size by 1.2% so that it now stands at 2,071,532 KB. Other statistics are as follows:
Disk volumes defined: 9
Folder paths defined: 2,637
Thumbnail Records: 316,627
keywords defined: 68,130
keyword references: 1,804,477
User field defined: 3
User field references 47
Every time I've tried to use compression or remake the thumbnails after changing the preferences there has been an error and the size of the database ends up bigger than when I started.
This is another topic but how did you make thumbnails that big? Every time I've experimented with thumbnails over 120x120 pixels they start to become cropped. The bigger the thumbnail the more the more cropping.
Anything else I can do to save my database?
Daan van Rooijen:
Okay, I see you really have a whole lot of thumbnails.. I was hoping that a large part of your database would be occupied by old, erased thumbnails that hadn't been fysically purged from the database file yet.
Your questions about converting to SQLite3, or externalizing the thumbnails were certainly good, but I don't have the answers to them.
Have you tried Database | Jpeg Compress? (of course, keeping a backup of your current database). For now, that would seem like the best solution to me. It should greatly reduce the database size.
Also, are you sure that simply starting a new database is no option? I see that you have a lot of keywords and if those were painstakenly entered by hand, I can see how you don't want to lose them. But if they were auto-generated maybe you can just start a new database (in SQLite 3 format if you wish).
> This is another topic but how did you make thumbnails that big? Every time I've experimented with thumbnails over 120x120 pixels they start to become cropped.
Changing the thumbnail size doesn't affect your existing thumbnails - those will still be 96x96 until you re-make them. So, that's why they may look cropped. Just select a few and press F3 to see what your thumbnails will look like once you rebuild them. Of course, thumbnails for new files will also be built at the new, larger size that you set.
Greatly Perturbed:
> Have you tried Database | Jpeg Compress? (of course, keeping a backup of your current database). For now, that would seem like the best solution to me. It should greatly reduce the database size.
Thanks, but Jpeg Compress is useless. Compressing to 50% saves around 1 MB:
The database compact and repair process succeeded.
Old size: 2,147,483,648 bytes
New size: 2,146,553,856 bytes
Compressed by: 0.0 %
> Also, are you sure that simply starting a new database is no option? I see that you have a lot of keywords and if those were painstakenly entered by hand, I can see how you don't want to lose them. But if they were auto-generated maybe you can just start a new database (in SQLite 3 format if you wish).
Most of the keywords were auto generated but I don't want to lose my user-generated fields, keywords, galleries and searches. I did try starting to create a new database in SQLite 3 format but gave up because of the slow time to create thumbnails.
Regarding Thumbnail size regardless of whether it is a new database or I rebuild thumbnails any size over 120 is cropped. I've no idea how you can make good large thumbnails.
Navigation
[0] Message Index
[#] Next page
Go to full version