Lightroom: Catalogue Alternative Database Choice

  • 3
  • Idea
  • Updated 2 years ago
  • (Edited)
I would like to have the OPTION to specify my own Lr catalogue database. SQLite is great to a degree, and I fully appreciate why it is used - licensing, distribution and embedding etc. I also use it a fair bit. However I'd also like to be able to specify SQL Server or MySQL, for example and offload the catalogue from my PC onto a proper industrial-strength database engine and then you have the facility for other people to access the same catalogue based on permission structures and roles. MySQL can be embedded and distributed, but I run it on several servers. It's been my favorite database for years, and proper database backups and restores are easier - it's just better all round for large catalogues.

I could have several people processing images in the same catalog, you wouldn't be quite so retricted to 60k-100k images per catalog - which is possibly the SQLite limit - and all images could be accessible via a web application, so others could search on the same groupings as L3 uses and any additions are live immediately. I could also easily produce reports on latest images, image counts, keyword counts, etc independantly of Lr.

All it would need are some initial build scripts and the connection string, after all you need a connection string to SQLite don't you? Don't know if running across a network would pose problms though.
Photo of wewerethere

wewerethere

  • 1 Post
  • 0 Reply Likes

Posted 6 years ago

  • 3
Photo of Lee Jay

Lee Jay

  • 990 Posts
  • 134 Reply Likes
Several people have over 500,000 images in their current LR catalogs.
Photo of jdv

jdv, Champion

  • 728 Posts
  • 56 Reply Likes
SQLite has no such explicit or implicit limits. Also, this is not as simple as plugging in another DB. SQLite wins because it can be so easily embedded and heavily tweaked. And the Lr database instance is very heavily tweaked.

Basically, if you are seeing issues, blame the app or the environment. Because it isn't the underlying DB tech.
Photo of Jaime Visser

Jaime Visser

  • 1 Post
  • 0 Reply Likes
Why not make Lightroom use mySQL as an alternative backend to the current SqLite lrcat files? This would make multi-user environments possible, a much requested feature.

This reply was created from a merged topic originally titled
Multi-user Lightroom storage.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3589 Posts
  • 928 Reply Likes
See the comments by employee Dan Tull in this thread, who explains that the choice of database backend isn't the driving issue in whether or how to make LR multi-user/multi-computer:

http://feedback.photoshop.com/photosh...
Photo of Bryn Forbes

Bryn Forbes

  • 157 Posts
  • 21 Reply Likes
I have a catalog with over 900,000 images. It works pretty well. Of course I'd always love for it to be faster!
However, I know how difficult it is to support and tune an application on different databases so I'm not sure if that effort would be more useful than the manpower devoted to further sqllite optimizations
Photo of Bryn Forbes

Bryn Forbes

  • 157 Posts
  • 21 Reply Likes
perhaps for people who have a lot of ram, there could be a preference to increase the sqlite page cache size, or load the entire database in to ram on startup.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3589 Posts
  • 928 Reply Likes
I think it's likely that if you have a lot of memory, the operating system will end up quickly caching all the important bits of the database file in memory in any case, so there wouldn't be a large advantage to explicitly loading it into memory.