Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!samsung!sol.ctr.columbia.edu!cica!iuvax!bronze.ucs.indiana.edu!mdchaney
From: mdchaney@bronze.ucs.indiana.edu (M Darrin Chaney)
Newsgroups: comp.databases
Subject: Re: Why is Oracle better than Ingres
Message-ID: <76172@iuvax.cs.indiana.edu>
Date: 4 Dec 90 18:29:58 GMT
References: <734@keele.keele.ac.uk> <5550@avocado20.UUCP> <1990Dec2.080257.21343@odi.com> <1338@vision.UUCP>
Sender: news@iuvax.cs.indiana.edu
Reply-To: mdchaney@bronze.ucs.indiana.edu (M Darrin Chaney)
Organization: Indiana University, Bloomington
Lines: 22

In article <1338@vision.UUCP> chris@vision.UUCP (Chris Davies) writes:
>In article <5550@avocado20.UUCP> palat@motcid.UUCP (Mohan Palat) writes:
>> Oracle uses an unusual process architecture (in UNIX). Several 
>> processes have to be started up before one can even access a 
>> database. Ingres does not require any such initialization. 
>
>In version 6.x of both Ingres and Oracle (and Informix/Turbo too) you need 3
>or 4 processes running as daemons before you can access any database.  This
>situation is not just true for Oracle.  Please check your facts before posting!

Ingres 6.x has 6 processes that run detached, at least under VMS.  These are
necessary to do database access, as well as handle internode communication,
synchronization, etc.  Also, it usually creates a subprocess when someone
runs Ingres.

This really isn't some big, bad thing, IMHO.

	Darrin

mdchaney@iubacs
mdchaney@bronze.ucs.indiana.edu
mdchaney@rose.ucs.indiana.edu


Brought to you by Super Global Mega Corp .com