Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!usc!ucsd!pacbell.com!pacbell!rtech!ingres!sergio
From: sergio@ingres.com (Sergio Aponte)
Newsgroups: comp.databases
Subject: Re: Ingres and NFS
Message-ID: <1990Oct31.174509.14988@ingres.Ingres.COM>
Date: 31 Oct 90 17:45:08 GMT
References: <4691@spdcc.SPDCC.COM> <1990Oct30.151205.5406@oracle.com>
Reply-To: sergio@squid.Ingres.COM (Sergio Aponte)
Organization: Ingres Corporation, Alameda CA 94501
Lines: 25

In article <1990Oct30.151205.5406@oracle.com> kbittner@oracle.UUCP (Kurt Bittner) writes:
>In article <4691@spdcc.SPDCC.COM> dyer@ursa-major.spdcc.com (Steve Dyer) writes:
>>
>>I've heard that Ingres rel 6 "doesn't work" on NFS.  I'd like
>>to get a better restatement or a refutation of the problem. 
>>
>
	The suported use of NFS is for client installations to run clients
	(or front ends, as they used to be called). You install Ingres on the
	server node, and NFS mount to a client node, and you run the clients
	processes on it, not the DBMS. The DBMS should run on the server node,
	and you should use Ingres/NET to access the DBs. That way, you use the
	CPU on the client to run the client processes, and keep consistency on
	your DB by using the server DBMS on your server node.

	In this scenario, NFS saves you from having many installations of Ingres
	eating up disk space. Good use for it.

/* As before, this is my own contribution and in no way an official statement
   from ASK Computers, Ingres Division */
--
-------------------------------------------------------------------------------
| Internet: sergio@squid.ingres.com      Sergio L. Aponte, MTS @ Ingres Corp. |
| UUCP    : {sun,mtxinu,pyramid,pacbell,hoptoad,amdahl}!ingres!squid!sergio   |
-------------------------------------------------------------------------------