Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ukma!rutgers!sunybcs!canisius!elgie
From: elgie@canisius.UUCP (Bill Elgie)
Newsgroups: comp.databases
Subject: Re: Ingres Phasing Out at Berkeley
Message-ID: <2370@canisius.UUCP>
Date: 25 May 89 14:15:30 GMT
References: <24519@agate.BERKELEY.EDU> <3560039@wdl1.UUCP> <24756@agate.BERKELEY.EDU>
Organization: Canisius College, Buffalo N.Y. 14208
Lines: 46

In article <24756@agate.BERKELEY.EDU>, steve@violet.berkeley.edu (Steve Goldfield) writes:
> 
> #>	SO - what are they replacing INGRES with?  Postgres?
> 
> As far as I know, it isn't being replaced by any other
> database on the university's cluster of VAXes.

  So it doesn't seem like there is much need for a dbms, period.

> In fairness, I should mention that my group was the main one using Ingres 
> on the university machines and probably the only one paying for it in hard
> cash, so our decision to move to a cheaper department machine was probably 
> the principal cause of dropping Ingres. 

  oh.

> Still, I find it ironic that here in Berkeley, where Ingres was born, it 
> doesn't get much respect.

  Because you are not using it ?  (Does this mean that if YOU decide to use
  something other than Berkeley UNIX, that will be "ironic" also ?)
> 
> .... it appears that commercial
> versions of Ingres on other machines are better-supported
> (e.g., having gone to Version 6.0). 

  My site and the others that I am involved with are running version 5.  Sup-
  port seems to be fine.  I haven't seen or heard anything that indicates
  that there is some mystical connection between support and version 6. 

> I assume that
> in a corporate environment in which the company has outright
> purchased a computer and perhaps dedicated it for Ingres' use,
> exorbitant charges for cpu time are not as relevant as they
> are for us in which we pay, in cash, for our usage. 

  Sounds like you've got more than one bad guy out there to deal with.  

  We're far from a "corporation".  But that is the route we took: converted
  from a time sharing site's dbms to INGRES and purchased a machine for $35k
  to run INGRES backends.  We would have done the same even if we had selected
  someone else's dbms (provided their distributed data base facilities worked 
  as well): we have complex applications with complex retrievals.  These can
  require a lot of cpu.  There is no magic here, either.

  greg pavlov (under borrowed account), fstrf, amherst, ny