Since I see that several of the more experienced Allbase listers have not jumped in,
I'll take a stab at these questions. I am a fairly new Allbase administrator, so my
comments must be with some caution.

<<       1. What disk space is required of ALLBASE/SQL databases?  Is this a
high disk usage product?>>

Once an Allbase DBE is created, the process of attaching one or more TurboImage data
bases occupies exactly zero sectors. The DBE itself occupies a trivial amount of
space until native Allbase tables are added.

<<       2.  How is disk I/O performance effected by accessing IMAGE from
ALLBASE and conversely ALLBASE by the PC clients?>>

We have several applications that access some TurboImage data bases from applications
or portals on an HP9000. The project manager says that there are about 1,000 hits a
day. We see no impact at all. The regular TurboImage users have not complained a bit.

<<       3.  What load does ALLBASE place on the HP3000 CPU?>>

None that we have noticed. I realize that there has to be some load, but it is
insignificant.


<<       4.  Of those using ALLBASE/SQL, what has been your experience with
it?>>

Rather good. I would strongly urge you to take the appropriate Allbase training
courses. While careful reading of the manual will help, integrating the technical
commands with the concepts is difficult without guidance. I say this from personal
experience. I could not have gotten through this past year without the kind and
generous help from several people on the HP3000-L. This note of mine is a drop in the
bucket of pay back to these people.

There are several utilities to create, maintain and  measure Allbase, with no
consistency of syntax from one to the other. That makes it tough. Fortunately, the
HELP facilities are rather good, so I have not even tried to memorize even some of
the basic commands.