Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!mtxinu!sybase!shalom!loyer
From: loyer@shalom.sybase.com (George Loyer)
Newsgroups: comp.databases
Subject: Re: Sybase question
Message-ID: <11444@sybase.sybase.com>
Date: 23 Oct 90 14:51:05 GMT
References: <7170.271c55b3@swift.cs.tcd.ie>
Sender: news@Sybase.COM
Organization: Sybase, Inc.
Lines: 28

In article <7170.271c55b3@swift.cs.tcd.ie> ombhurley@swift.cs.tcd.ie writes:
>A friend of mine is working on a project and  asked me to try and get some info
>for him.
>The project involves data aquisition, processing and storing and uses as its
>information core the Sybase product. It runs on a 25MHz 386 + 387 with 8M 
>main mem and 110M hard storage. Sybase is installed on a raw partition that's
>about 30M in size. There is not extensive use made of interactive SQL, most
>of the database dealings involve use of library routines from continually
>and sporadically running C programs. (ie. some are continually logged into
>the database, others log in and out as necessary).
>
>p.s. the machine is running Interactive Unix 386
>
>The problem(s) is(are) thus:
>
...

This problem is complex enough that you should be talking to Sybase
Technical Support (in London, for your Dublin friend). Here in the
USA Technical Support Center we have seen at least one problem that
has (somewhat) similar symptoms and for which a fix is available, but
there are enough differences that your friend would benefit much from
working with the Support Center.  

George Loyer
Director, Technical Support Center
Sybase, Inc.
Emeryville, CA