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

Home -> Community -> Usenet -> c.d.o.misc -> Re: Avoiding any locks in SQL Servers - read and understand....itsmagic.

From: Guido Stepken <g.stepken_at_t-online.de>
Date: Fri, 05 Sep 2003 13:00:16 +0200
Message-ID: <bj9qao$hca$00$1@news.t-online.com>

Hi Noons !

You are right, in Oracle many can read and one write ;-)) This was one of the main reasons, oracle became famous. In MS SQL Server 2000, in 3 of 4 transaction variants, readers are blocked. Bad, very bad design.

cheers, Guido Stepken

Noons wrote:
....
> WITH DEFAULT ORACLE LOCKING, A READER IS NEVER, NEVER, NEVER,
> NEVER, NEVER, NEVER, NEVER, NEVER, NEVER, NEVER, NEVER, NEVER, NEVER
> BLOCKED BY A WRITER OR ANY OTHER READER.
>
> Got it now? Your phrase above should read:
> "but *many* can read and one write".

....
> That will come in useful for updating bank accounts:
> "transactions are simply dropped"?
>
> Cheers
> Nuno Souto
> wizofoz2k_at_yahoo.com.au.nospam
Received on Fri Sep 05 2003 - 06:00:16 CDT