Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site osiris.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!lll-crg!gymble!umcp-cs!aplcen!osiris!eric
From: eric@osiris.UUCP (Eric Bergan)
Newsgroups: net.database
Subject: Re: IBM DB2 lacks record locking
Message-ID: <583@osiris.UUCP>
Date: Thu, 31-Oct-85 08:06:05 EST
Article-I.D.: osiris.583
Posted: Thu Oct 31 08:06:05 1985
Date-Received: Sun, 3-Nov-85 10:30:56 EST
References: <941@ptsfa.UUCP>
Organization: Johns Hopkins Hospital
Lines: 17

> From Datamation, October 15 issue, page 13:
> 
> "... Notably absent so far from [DB2] has been an effective record-level
> locking feature that is critically important for performing simultaneous
> updates to a single database."
> 
> And we thought that only Unix DBMS's had problems with record locking :-)

	Also from that same article, it reports that DB2 is averaging
3 to 5 transactions per second on a mainframe. It goes on to quote the
same sources as saying they see 80 tps from IMS. The last numbers I saw
for Ingres on a supermini indicated it could handle around 10 tps.

-- 

					eric
					...!seismo!umcp-cs!aplvax!osiris!eric