Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!ptsfa!well!ustel
From: ustel@well.UUCP (Mark Hargrove)
Newsgroups: comp.databases
Subject: Re: Unify 3.1D
Message-ID: <4518@well.UUCP>
Date: Sun, 22-Nov-87 23:49:00 EST
Article-I.D.: well.4518
Posted: Sun Nov 22 23:49:00 1987
Date-Received: Thu, 26-Nov-87 00:06:14 EST
References: <119@ecs.ecs.oz>
Lines: 33

> 
> 
> 
> 	We have found from experience that our version of Unify 3.1D
> appears to crash (randomly writes records into wrong places, quietly,
> with no complaints) when the database size exceeds a magic number
> somewhere near 45000 blocks.
> 	If this is a problem anyone else has found, and if so
> do you know the magic number ?
> 	Do Unify 3.2/4 suffer from these problems ?

*3.1D* ?  Whew.  I can only guess that you must have been off of
your support contract for some time.  I recently dusted off and
converted a 3.1-vintage database to 4.0 which was roughly 48000
blocks -- we'd seen no problems with it during it's initial life
under 3.1. (er...what exactly do you mean by a 'block'? 512 or 1024?)
What machine type are you running?  Which OS?

My previous employer has a 3.2 (recently converted to 4.0) database
that's roughly 60MB right now -- no problems have been seen at all.

I strongly suggest, if you can do it, that you upgrade immediately
to Unify 4.0.  It's simply better, faster, and more wonderful than 
ever :-).

--Mark Hargrove


-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Mark A. Hargrove                                             U.S. TeleCenters
Voice: 408-496-1800                                          Santa Clara, CA
uucp : {dual, hoptoad, hplabs, portal, ptsfa}!well!ustel