Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!pasteur!ucbvax!decwrl!pyramid!voder!wlbr!mh
From: mh@wlbr.EATON.COM (Mike Hoegeman)
Newsgroups: comp.databases
Subject: Re: LAN Database Server products
Message-ID: <11832@wlbr.EATON.COM>
Date: 22 Apr 88 03:56:40 GMT
References: <281@syntrex.uucp>
Reply-To: mh@wlbr.UUCP (0000-Mike Hoegeman)
Organization: Eaton IMS, Westlake Village, CA
Lines: 32
Keywords: Server

In article <281@syntrex.uucp> rich@syntrex.uucp (Rich Birnbaum) writes:
>
>	I am looking for an RDBMS containing a dedicated Database Server.  
>The server would receive SQL commands from workstations, process them, and
>send any results back to the workstation.  The server is a separate
>machine (PC/AT) on the LAN.  Our LAN of choice is Banyan VINES so the database
>should work on VINES.  I have already spoken with Gupta Technologies
>in Menlo Park, CA.  They have such a product but it uses NETBIOS to
>communicate.  I would prefer a product that uses TCP/IP / Sockets.
>	Oracle is working on such a product but it is not yet available.
>	ANY help would be most appreciated.

We use sun's with sql*net (oracle's network interface which uses tcp)
here's some notes about it that you might want to know about it if you decide
to look into the oracle product.

- each connection chomps up about .7 meg of memory on the server
  (not sure what you'd use on an AT but it's probably something similar).

- you cannot use long column types across the network
  (you can cast a long into a char field however.) this means the biggest
  column you can ever get across the net is 240 characters.



our sun's have 8 meg. of memory in them so the first note does'nt
really affect us too much. 

all in all we're pretty happy with sql*net 
hope this is of some help to you.


-mike