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

From: Guido Stepken <stepken_at_little-idiot.de>
Date: Mon, 18 Aug 2003 20:48:35 +0200
Message-ID: <bhr74o$36m$03$1@news.t-online.com>

Hi, Aron !

Sorry, if forgot to say, that the client is immediately informed, that the data is written, although the server has them still in work within transaction, which may have been delayed, till other transactions are finished. From Client point of view, the server works like a charm, no locks, no errors, hispeed.
The merge replication in SQL Server 2000 with MSDE is similar, its like MVTO on a single table. MR rearrages updates and merges them into the master server. With true MVTO also there is a timestamp on transaction itself, so that updates on many tables are handled correctly.

regards, Guido Stepken

Aaron Bertrand - MVP wrote:

>>possible to delay one transaction as long, as the other transaction
>>writing into the database.

>
>
> What is the big evil of a lock? Making a user wait for the lock to be
> released. So, what is the difference between a lock, and the sequence of
> events you describe above? In both cases, there is a delay...
>
>
Received on Mon Aug 18 2003 - 13:48:35 CDT