Path: utzoo!attcan!uunet!wuarchive!cs.utexas.edu!tut.cis.ohio-state.edu!uc!shamash!tank!delphi!monty
From: monty@delphi.uchicago.edu (Monty Mullig)
Newsgroups: comp.databases
Subject: Re: Client/Server processes and implementations
Keywords: Client Server Processes
Message-ID: <6461@tank.uchicago.edu>
Date: 29 Nov 89 07:05:10 GMT
References: <7114@sybase.sybase.com> <6895@sybase.sybase.com> <2184@kodak.UUCP> <6434@tank.uchicago.edu> <4178@rtech.rtech.com>
Sender: news@tank.uchicago.edu
Reply-To: monty@delphi.UUCP (Monty Mullig)
Organization: Univ. of Chicago, BSD Info. Systems
Lines: 24

In article <4178@rtech.rtech.com> wong@rtech.rtech.com (J. Wong) writes:
>Yes, INGRES 6.1 is available today on the Sun 4 (SPARCstation)
>and does include stored procedures as a feature.  Talk to your
>Sales Rep!
>
>J. Wong		wong@rtech.com		Ingres Corporation.

yes, mr. wong, i talked to my sales rep and he told me that ingres 6.x
was available for my suns, but my pc clients would need to run ingres
5.x since the pc ingres conversion to 6.x hadn't been made yet.  he
also told me that a "gateway" between 5.x on the pcs and 6.x on the
suns was available, but that he "couldn't guarantee its reliability".
moreover, people from our business school who ran 6.1 ingres were very
sceptical about the stability of the backend, so much so that they
wouldn't recommend it to us and that they felt that they had to keep
their production systems in 5.x.

i don't want a buggy, unstable backend.  i want a mature, stable
backend that can support my pcs frontends without awkward,
unguaranteeable bridges.   semi-solutions don't work with my users.
and your product hasn't shown itself to be as stable or mature in my
environment (sun servers and pc frontends) as sybase.

--monty


Brought to you by Super Global Mega Corp .com