I have cross posted this question to listservs: HP3000-L and SPEEDWARE...
 
I am looking for guidance from other DBA's running Allbase in a production
environment (preferably using Speedware).
 
Problem:
-------
In the middle of the production day an important fileset fills.
 
The fileset is ENROLLMENTFS with ENROLLMENTD (502 pages) and ENROLLMENTI (879
pages) which holds table ENROLLMENT, unique index ID_ENROLLMENT ; non unique
indexes ID_CONTRACT, ID_EDUC-PRODUCT, ID_STUDENT.
 
This arrangement was created as a result of Speedware's Designer knowing that
the max number of records (tuples) in the table was to be 10,000.
 
To resolve the immediate need, I created 2 additional DBEFILEs: ENROLLMEN2D
(1004 pages) and ENROLLMEN2I (1758 pages) which effectively triples the
original space (in terms of pages).
 
Questions:
---------
 
1) Is there any advantage/disadvantage in UNLOADING the data, regenerating a
single pair of Data/Index DBEFILEs  with 3 times the size of the original
ENROLLMENTD and ENROLLMENTI files, and then LOADING the data back in?
 
2) If I leave the ENROLLMEN2D & ...2I files in place and perhaps add to it in
the future, is there some means of determining from the number of pages
allocated, the maximum number of records (tuples) that could be held in the
fileset?
 
3) What is the general practice in Speedware and non-Speedware shops?
 
Still new at this stuff...
\rjh
 
 
-----------------------------------
Robert Hilverth, I.S.P.
Database Administrator
Mohawk College of App. Arts & Tech.
PO Box 2034
Hamilton, Ontario
Canada     L8R 3T2
Tel: 905/575-1212 x3052
Fax: 905/575-2378
 
Internet:
   [log in to unmask]
-----------------------------------