[comp.databases] Opinions wanted on choosing a new RDBMS

fpb@ittc.wec.com (Frank P. Bresz) (11/01/90)

Hello,

	I am in the process of evaluating a new RDBMS for our department
~200 people.  We are currently using UNIFY.  We have noticed some
limitations in the implementation and are finally at a point where we can
consider alternatives.  The main 4 we are considering are ORACLE, INFORMIX,
INGRES, SYBASE.  

	Information perhaps to help with your input.  We run primarily on
Sun workstations but will be moving onto DECstations fairly soon.  We do
have a medium amount of data to sling around.  When we dump it out into
ascii files we end up with about 9 Megabytes of data.  UNIFY keeps all of
this data in a single binary file exceeding 31 Megabytes of data (what a
lose).

	It is absolutely terrible at string fields (no editting).

	We have about 1300 fields in 60 records (tables) that currently
rely heavily on UNIFY and the relation field concept they have implemented.

	I am interested in any and all information people have.  Good, Bad,
Flames, Raves.  I am highly technical and would appreciate some tekkie info
on C Language interface, 4GL, Reporting capabilites, SQL (how fast, how
'standard'). 

	Thank you very much.
--
| ()  ()  () | Frank P. Bresz   | Westinghouse Electric Corporation
|  \  /\  /  | fpb@ittc.wec.com | ITTC Simulators Department
|   \/  \/   | uunet!ittc!fpb   | Those who can, do. Those who can't, simulate.
| ---------- | (412)733-6749    | My opinions are mine, WEC don't want 'em.

fpb@ittc.wec.com (Frank P. Bresz) (11/02/90)

Hello,

	I am in the process of evaluating a new RDBMS for our department
~200 people.  We are currently using UNIFY.  We have noticed some
limitations in the implementation and are finally at a point where we can
consider alternatives.  The main 4 we are considering are ORACLE, INFORMIX,
INGRES, SYBASE.  

	Information perhaps to help with your input.  We run primarily on
Sun workstations but will be moving onto DECstations fairly soon.  We do
have a medium amount of data to sling around.  When we dump it out into
ascii files we end up with about 9 Megabytes of data.  UNIFY keeps all of
this data in a single binary file exceeding 31 Megabytes of data (what a
lose).

	It is absolutely terrible at string fields (no editting).

	We have about 1300 fields in 60 records (tables) that currently
rely heavily on UNIFY and the relation field concept they have implemented.

	I am interested in any and all information people have.  Good, Bad,
Flames, Raves.  I am highly technical and would appreciate some tekkie info
on C Language interface, 4GL, Reporting capabilites, SQL (how fast, how
'standard'). 

	Thank you very much.

	P.S. I forgot to add that I don't get this newsgroup yet so email
is preferrable for your responses.

--
| ()  ()  () | Frank P. Bresz   | Westinghouse Electric Corporation
|  \  /\  /  | fpb@ittc.wec.com | ITTC Simulators Department
|   \/  \/   | uunet!ittc!fpb   | Those who can, do. Those who can't, simulate.
| ---------- | (412)733-6749    | My opinions are mine, WEC don't want 'em.

--
| ()  ()  () | Frank P. Bresz   | Westinghouse Electric Corporation
|  \  /\  /  | fpb@ittc.wec.com | ITTC Simulators Department
|   \/  \/   | uunet!ittc!fpb   | Those who can, do. Those who can't, simulate.
| ---------- | (412)733-6749    | My opinions are mine, WEC don't want 'em.