Path: utzoo!attcan!uunet!mcsun!hp4nl!charon!johan
From: johan@cwi.nl (Johan Wolleswinkel)
Newsgroups: comp.databases
Subject: Re: Use of INGRES in a SUN environmnet
Message-ID: <2132@charon.cwi.nl>
Date: 18 Sep 90 08:28:11 GMT
References: <1990Sep17.150529.4468@cs.umu.se>
Sender: news@cwi.nl
Lines: 51

krn@cs.umu.se (Kenneth Nilsson) writes:


>We are now installing INGRES version 6.2 (including INGRES Net on SUN 
>(4/490 servers and SPARC SS1 diskless work stations) and have some questions 
>concerning the best way to organize the use of INGRES for a large number 
>of students.

> [ ... ]

>+ Kenneth Nilsson                               + usenet address:        +
>+ Institute of Information Processing           + krn@cs.umu.se          +

We have the same situation here: lots of Sun workstations (ca. 80),
with lots of users (ca. 200) which will occasionally use an
Ingres application, preferably from their own workstation,
but in principle from any.

It turns out, that version 6.3, which is already available,
is much better tuned to this situation.
Ingres environment variables can be set globally for all
workstations, the files-directory can be (easily) shared,
there is a new directory in the Ingres-dir.tree for the
client-specific information.
   If you intend to start using 6.2 I would strongly advise
   to switch straight to 6.3.

The problem of the host-specific netu-information still
exists in this version. It's quite amazing, that one of
the strong points of Ingres (the easy way of sharing DB's
among different processors), is bothered so much by a seemingly
simple administrative matter.
We expect to solve the problem by linking the corresponding
client-specific netu-files; this may cause problems in case of
parallel update of netu-information, but prefer this very small
chance over the other apparent approaches:
-  having each user run for each workstation (80 !) the tedious
   netu-sequences, OR
-  having each user keep his own administration on which workstation
   he ran allready netu, and running it for the others when needed, OR
-  having each user be confronted by the terrifying sequence of
   Ingres messages in case of running an application without a netu.

However, we haven't got any experience with this setup,
and are interested in other solutions (and finally of course in
a real solution from Ingres!).
--
                                                    Johan Wolleswinkel
CWI, Postbus 4079, 1009 AB  Amsterdam,  Kruislaan 413, The Netherlands
Phone: +31 20 5924122    Fax: +31 20 5924199   Telex: 12571 (mactr nl)
Internet:   johan@cwi.nl            or          ...!hp4nl!cwi.nl!johan