Catalog Corruption

In the midst of all the Beta 2 excitement, I've a post on a version 1 issue. Beta 2 is not ready as a production tool so I've still doing my work in V1.0.
I've finally gotten a mix of time and motivation to finish a new site for my main website, that is until Lightroom started doing very strange things. I've noticed a slowdown recently, so I figured I could do with optimising the catalog. I'd skipped the backup when I last started (I know, I know), so I let it run this time just in case.

Lightroom went through the integrity check slowly, in fact so slowly, I opted for bed rather than wait on it. As I said in the Beta 2 post, I decided to sleep out the announcement. When I woke this morning and checked the computer, I was greeted with this ominous message:

I checked the technote by clicking on the link. It leads to this page. An interesting read. I've had a lot of catalog churn recently with organisation, along with Web Gallery creation, so I've been restarting and occasionally having to force quit Lightroom. Somewhere along the way the catalog had become corrupted. Knowing that Dan Tull has put a lot of work into catalog rescue, I figured that either the repair would work, or Dan would have another test catalog. I wasn't worried as I have a recent backup. So I clicked 'Repair Catalog' and let Lightroom work away.

After a while the delightful news came back:

Phew. I'm glad my faith was justified! Instances like these prove that even with a good system, things can fail, so back up!

The Catalog Conundrum

This week has seen John Beardsworth weighing in on Ken Milburns 'Inside Lightroom' post on using Catalogs. John is quick to point out some of the failings of a multicatalog approach. Ken advocates having a different catalog for each genre he would've had in a main catalog.
It's all very well in theory, but the whole idea of having a program that manages your images, is that you let it manage all of your images. John is right in saying that a central catalog is the best way.

My personal recommendation is that if you have a job that requires a speedy selection and processing workflow, by all means use a fresh catalog on a recently restarted machine. Once the selections are made and the processing is done, delete the rejects and import this into your main catalog.
There are people out there with 300,00 images in their catalog. They use fast machines and therefore have lesser speed issues.
Personally my main catalog doesn't contain all my images-yet. I need time to get them all in. Currently I've been hovering around 65,000 images. I've been deleting old rejects as new images come in and the number stays fairly balanced. Having one main Library means I can access any image quickly. I recently shot an aerial job for someone that had a Ferrari. As we discussed the aerial job, he enquired if I had any old photos of the car. I was able to tell him instantly that I had shots of it as both a red and yellow Ferrari (he had a spray job done). This couldn't happen with a multi catalog setup.

So for me one main catalog file is the way to go. I still use temporary catalogs for quick jobs and import the keepers to the main catalog for reference. I'd love a command to consolidate my library onto one chosen drive though, especially as the files out grow the mix of internal and external disks I now own.