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

From: Guido Stepken <stepken_at_little-idiot.de>
Date: Tue, 19 Aug 2003 12:46:59 +0200
Message-ID: <bhsv9m$s6p$01$1@news.t-online.com>

lello, Dieter !

Try the following:

Continuously write into the database rows in a endless loop with transactional mode set to SERIALIZE, COMMITTED ..., and then try with any client to read from the database. You will be blocked. Not so with PostgreSQL, Firebird, LogicSQL, Oracle.
Then do a export of data into a file, a backup, during the write loop. You will see.

PostgreSQL documentation you find everywhere, search google.

Look also at LogicSQL documentation, it is very well described MVCC, MVTO.

There are lies, damn lies and Microsoft !!!! SQL Server can easily be hunted down in benchmarks....feel lucky, if the system works without chaotic, undeterministic hangups.

regards, Guido Stepken

Dieter Nöth wrote:
> Guido Stepken wrote:
>

>> With a simple benchmark test i can show, that SQL Server breaks down 
>> at minimum load. 

>
>
> You know, there are lies, damn lies and benchmarks...
>
> > Oracle is much better at read-write (not at write-write),
>

>> PostgreSQL with abolute independant MVCC (write-write, write-read ist 
>> possible, without any locking...) is hitting the top. No locks have to
>> be set in PostgreSQL, but - MVCC is the minimum requirement to 
>> implement MVTO. 

>
>
> Please point me to the PostgreSQL documentation where this is descibed.
>

>> Setting timestamps on transactions and datasets, so a server side 
>> logic can time - shift transactions and rearrange data content, as if 
>> a lock had been set. This is a simple script in pl/SQL.

>
>
> Dieter
>
Received on Tue Aug 19 2003 - 05:46:59 CDT