Re: Avoiding any locks in SQL Servers - read and understand....its magic.

Guido Stepken <stepken_at_little-idiot.de> wrote in message news:<bhserr$26q$00$1_at_news.t-online.com>... []
> Locking is not neccessary, database performance increases very much,
> because clients (and server) do not have to wait for any lock to be
> released.
>
> If you still want to lock rows for many client access, make yourself
> clear, that you are programming with a technology, coming from stone age
> of database programming. Live with it, waist money, believe, you're on
> the right way.
>
> Say goodbye to locking, its not elementary for any business process.
[]
>
> regards, Guido Stepken
>

You're mistaken about locking not being fundamental to some business processes. You misapplied a similar, but not analogous process.

 There are operations that only work in the real world by locking. Consider a PAPER Work Order (ever been to a garage before computers?). Just by the physical nature of it, the person holding the paper has a lock on it. There are many similar cases in transaction processing. DBMSs allow more people to have access to that work order, but there is still a fundamental locking nature to the process.

So your basic premise is wrong, proof about traffic circles over lighted intersections notwithstanding.

 Ed Received on Tue Aug 19 2003 - 12:46:09 CDT