Hi David,

As a user who needs to shuffle multi-GB database files on a regular
basis, I have to put in some stipulations about any 'automatic' file
creations.

First, for ease of maintenance, we set our maximum file size to 640 MB.
This is alot less than 2GB.
Second, the new file may need to be created once a certain size is
reached in the last file.
For example - you have a setting that is the prefered file size and a
file size trigger - both user configurable and updatable.
So, I want standard files of 1GB in size but that the next file is to be
automatically created once the current file grows past 750 MB.
Also, you would want some notification to be sent to the system
administrator, and some notification in the logs.
You would also want to stipulate what paths are available and have the
file creation routine check for available space.

The above would make the auto-creation routines a useable feature vs a
feature that is ignored.

I could see this happening in another background thread vs happening
while a user is adding information to the database.

Perhaps the best way to handle this initially, would be to create a
(program/daemon/bot/service/nlm) that operates separite from the
database and on a timer, checks to see how the drive/file space is
doing. It could read system tables in the gdb for the currently active
databases (it would need to determine what databases are currently
active in the server) and perform the work using currently available
tools.

Such a utility should be made to work for all versions of IB and does
not add to the complexity of IB so it should not have the problem of
causing more bugs in a product we want to stabilize.

Also, since it is a outside utility, any developer could produce it
without having alot of internal database knowledge.

Just my 2c worth.

best regards

Dalton


David Berg wrote:

>
> Which brings us back to the point that my primary concern is manageability.
>
> In other words, if Interbase was capable of adding the additional files on
> an as needed basis (without operator intervention), then it's not as
> important for us to have support for files > 2/4GB.
>