Hi - I just updated PSu and database update has been running since yesterday evening (about 18 hours). It doesn't seem any nearer to completion but the dire warning 'please do not terminate while this message is shown it may permanently damage your database' has stopped me taking any action. Is this a realistic timescale or is something amiss? My original files and catalogue are on an external drive and the drive does seem to be showing activity (flashing) so maybe it really is taking this long? I have about 15k photos.
Thanks, Rhod
catalogue update taking ages after update
catalogue update taking ages after update
Last edited by Rhod on 26 Jan 23 16:21, edited 1 time in total.
Re: catalogue update taking ages after update
The progress bar hasn't moved since last night...
Re: catalogue update taking ages after update
I have had one or two updates that must have taken a similar time, so I'd stay with it.
Re: catalogue update taking ages after update
Hi,
how big ist your database and thumbs.db?
Do you have a file based BackUp? Have you compressed the database befor update? If so / if not you may abort, restore the database from the BU perform a cmpression and try again.
horst
how big ist your database and thumbs.db?
Do you have a file based BackUp? Have you compressed the database befor update? If so / if not you may abort, restore the database from the BU perform a cmpression and try again.
horst
Re: catalogue update taking ages after update
Hi - I compress my catalogue and thumbs pretty regularly. The catalogue db is 1.49gb and the thumbs db is 16.44gb. I will do as you suggest. Thanks
Re: catalogue update taking ages after update
I have a recent backup but if I try to start PSu without updating so that I can compress both dbs it closes.
Re: catalogue update taking ages after update
To be able to restore backup of the old version, you need to run it under the old version, so you need to downgrade, open the database, compress, install the new version, run.I have a recent backup but if I try to start PSu without updating so that I can compress both dbs it closes.
An alternative that you could try if you are running PSU as a standalone SQLite database:
Download SQLite Expert (free personal edition). Open both the PSU thumbs and catalog databases in SQLite Expert, run a vacuum (= compress) there and then try PSU (the newer version). SQLite Expert vacuum does not run all the same routines as PSU compacting, but it will result in a smaller database file that might need less time to upgrade.
Re: catalogue update taking ages after update
Thanks for the replies everyone - it did eventually finish updating!