P: Allow Catalog to be stored on a networked drive.

"From a user's perspective this is not relevant. As a photographer, I don't want to care about that kind of distinction. "

Agreed, users dont care as long as it works, but with these forums and the way the comments are spread, I think we are aswering comments in no particular order.

Axiom, you said these forums were made on SQL, point made 🙂

ok, to clarify, I did mean spinning (Powered on and spinning) as opposed to spinning disks in general. I do keep my images on spinning disk, Raided spinning disk which is then backed up twice. That's for my personnel work. For clients that i build workflows for, I tend to go 6Gbe Raid storage and LTO. Local lcats are then synced to the raid after each day with our friend Chronosync

"Think we're crossing Asset management, and DB management here"

From a user's perspective this is not relevant. As a photographer, I don't want to care about that kind of distinction. I want an integrated solution that makes my like easier. I want to be able to share my edits and metadata effectively with collaborators and be able to press a "do it" button that copies my files at the right place where I know they are safe.

Now, I am tech savvy so I know it is more complex. This is why I am suggesting ways of adding some very needed features so I don't have to spend my time assembling my own heterogenous and unsupported solution.

Yes, agreed this thread is becoming a nightmare to follow.. I need a drink..

So, why did you say that it is not a good option to store images on spinning drives? it looks like that is what you do too 😉

Again, i'm just answering a question you bought up. keeping to the OP, then it would have been closed and archived off months back :)

Adobe will not implement full blow SQL with shared collaborative working, as long as they have Revel, adobe drive and other 'sharing' apps

This thread is becoming impossible to follow, we are shooting in all directions ;)

I addressed that in another comment... check-in, check-out, all including pulling/pushing master files to a central repository, while keeping the local database option for portability.

"stuart, fyi... a regular hard drive in normal conditions will far outlast your ssd's. That's just a fact. And even still, a 5 terabyte rack of 5x 1t 7200rpm drives are far cheaper to replace per terabyte then the same in ssd's.
I can live with a cumulative delay of 5 minutes by days' end, whilst saving the hundreds of bucks."

I ONLY use SSD's for system drives, for normal storage, it'll either be SAS or some kind or SATA Raid.

But back my point, still is that hard drives DO and WILL fail.

i use isolinear rods.

:P

stuartpeckphoto - again, please let'ss tay relevant to the topic. I know how to setup an enterprise class backup solution. I also know that drives fail, which is why I have redundant copies of my data. I work on my laptop and I don't mount my archive drives all the time, just when needed.

But that still does not adress the LR shortcomings...

B.T.W. SSD's and flash cards do have a limited life span... No storage solution is bullet proof. Spinning drives are cheap so I can buy three and keep three copies and be safe. The day SSD's of terabytes+ capacity cost under 100 bucks, be sure I will go for them. For now, they are not cost effective for a large collection of images.

Still out of topic.