I've had to do a variety of schemes based on need.
- I had a system that interfaced with a telephone switch in real time and lots of updates would happen. We had to do automatic locking when updating the record. We had to reuse deleted records. The biggest problem was reindexing, especially considering the main table was about 1.7 Gig in size. Managing that was a big problem.
- I had another system with over 100 users. There were literally no updates or deletes, all inserts.
- Most other applications I just used default, pessimistic locking.
>Hi, Pertti,
>
>Thanks for your message. I'm curious to know how many developers out there are using optimistic vs. pessimistic. So far it seems a few more are using pessimistic, though I'm sure there are some on both sides. The main reason I go with pessimistic over optimistic is not because of technology, but because it's the most common approach that was needed.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer