Isn't it strange how problems like this are always the fault of the database and not the developer? :crazy:

Anyway, I'd be inclined to set up a trace on the server so you can see exactly what SQL commands are being executed and how long they're taking. It'll add a bit of extra load, obviously, but if anything that should make the problem happen sooner and thus be easier to trace!