Moving to new laptop. One of databases happen to be in .sparseimage instead of .dtBases2 (created long time ago, possibly in DT2).
I am trying to export it (and make .dtBase2) but DT says “Optimization of database failed” without producing any output.
The database itself seem to work fine, Verify & Repair went without any issues.
Please advise how can I convert into .dtBase2
Mount the sparse image in the Finder while DEVONthink is not running, then move the .dtBase2 database from the mounted volume e.g. to the desktop and unmount the volume. Finally double-click on the moved .dtBase2 database to open it.
thank you @cgrunenberg , it works. However DT can open .dtBase2 file without asking for password while .sparseimage requires password to open. Is that intended behaviour? I need the DB to be password protected.
Open a support ticket.
I think this is the way encrypted databases work. They are unencrypted, stored in an encrypted sparse disk image. As far as I know, Devonthink doesn’t ever encrypt databases. An encrypted database is a normal database inside an encrypted container (disk image).
Rename your .dtsparse file to .dmg and open it with the finder. That will require a password. You can either open the Devonthink database inside the disk image from there or drag it to another place on your computer.
Either way, the database itself isn’t encrypted.
One thing to keep in mind is if you sync an encrypted database to an unencrypted sync store it can be read without a password.
Also, when you download an database you want encrypted to a new computer, if you don’t download it as encrypted it will be in the clear on the new machine.
There are advantages to this. Devonthink is not creating its own crypto, it’s using Apple’s baked in encrypted disk image support. Plus, you have the chance to see what’s there beneath the encryption, if you want.
This is true but there is likely other trouble afoot here.
thank you @Amontillado , after some tinkering with the file I realised that is the way it does work.
The question why it can’t be exported stating Optimisation failed remains and ticket has been crearted as @BLUEFROG has suggested. thank you