At 03:52 PM 4/02/2004 +0000, you wrote:

> > I was thinking along the lines of disk management and, because I'm
>really a
> > mouse in Witch's Breeches, I'd take a lot of convincing to "push
>the
> > envelope" where partitioning the database is concerned. (And I
>don't want
> > the usual "hue and decry" from Mr Leyne regarding split databases
>vs
> > everything in one bowl...<g>) I treat massive single-file
>databases as one
> > of those "just because you can doesn't mean you should" kind of
>things,
> > until proven otherwise.
>
>We have some plans to have a few databases...

Ah, sure, but I am not talking about multiple databases. *One database*
can be split into multiple physical *files*. What I am talking about is
the practice of just letting a single database file grow to fit the limits
of the disk's capacity.

Fortunately, it is easy to split a database up.

One needs to consider the logistics of recovery strategies, in any event.

In the appallingly awful event that the database gets corrupted and needs a
professional hand to reconstruct it, one needs to anticipate the logistics
of transporting a single, huge database file from Sarajevo to Massachusetts...

/hb