Path: utzoo!utgpu!water!watmath!clyde!mcdchg!nud!anasaz!john
From: john@anasaz.UUCP (John Moore)
Newsgroups: comp.databases
Subject: Re: OLTP, New releases of Oracle and Rdb ...
Summary: Serious OLTP requires...
Keywords: OLTP, performance
Message-ID: <1156@anasaz.UUCP>
Date: 4 Aug 88 00:23:25 GMT
References: <376@cullsj.UUCP%
Reply-To: john@anasaz.UUCP (John Moore)
Organization: Anasazi Inc, Phoenix AZ
Lines: 23

In article <376@cullsj.UUCP% gupta@cullsj.UUCP (Yogesh Gupta) writes:
%than being THE buzzword for the industry, what makes or does not make
%a DBMS an OLTP system?  What really are the requirements of the OLTP
%market?  There have been studies that indicate that 95% of the customers
%need less than 20 TPS, when it comes to speed.  Is it realistic to expect
%to support 500 terminals on a VAX (any VAX) in the near future?

We are working on serious OLTP systems (large scale reservation systems)
using RDBMS technology. What we need is PERFORMANCE (1 res transaction
per second is about 25 TP1's!), AVAILABILITY (when it goes down,
its a real problem), and PREDICTABILITY (no transaction should take
very long because of unexpected behavior in the SQL optimzer).

It appears that PERFORMANCE is on everyone's list (ORACLE, INFORMIX,
INGRESS, UNIFY, SYBASE). AVAILABILITY is NOT! Some RDBMS's require
that the system be shut down to take backups. None that I am aware
of directly provide disk mirroring. PREDICTABILITY has not even
been mentioned in any of the literature I have seen.
-- 
John Moore (NJ7E)           {decvax, ncar, ihnp4}!noao!nud!anasaz!john
(602) 861-7607 (day or eve) {gatech, ames, rutgers}!ncar!...
The opinions expressed here are obviously not mine, so they must be
someone else's.