Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ukma!rutgers!sunybcs!canisius!elgie
From: elgie@canisius.UUCP (Bill Elgie)
Newsgroups: comp.databases
Subject: Re: Ingres vs Sybase
Message-ID: <2350@canisius.UUCP>
Date: 7 May 89 04:26:41 GMT
References: <4306@elecvax.eecs.unsw.oz>
Organization: Canisius College, Buffalo N.Y. 14208
Lines: 18

In article <4306@elecvax.eecs.unsw.oz>, ykchan@elecvax.eecs.unsw.oz (Yk Chan) writes:
> I am starting a database project on unix.  I have access to Ingres and Sybase.
> Anyone out there in the net has comment 
> on the pro's and con's of Ingres vs Sybase.
> Price is not an issue because I have access to both already.

  You are in an ideal situation: you have access to your range of choices.

  If the application is important, the absolutely best thing that you can do
  is to design and implement a subset of it under both dbms packages.  Throw in
  a few kinks (like several really large tables) to push the two.

  This should give you much more relevant information than reams of anecdotal
  info from people whose applications, end-user demands, and working style may
  bear no relationship to your's.

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