plinehan wrote:

> My understanding of the situation at the moment is that the
> only placement strategy one can pursue is putting the OS on
> one disk, the server on another, the temp directory on another
> and the database file itself on yet another.

Not really a good idea. If you have a dedicated DB server, OS and server
files are read only once, at system startup and never touched again.
Having a separate disk for that is simply not needed. You need 2 disks
at most: one for OS+server+temp_space and other for database.

> This has the major disadvantage of, for example, not allowing
> the DBA to put infrequently updated tables on one of the
> 3 other disks to really optimise disk usage for "hot"
> tables.

Not a bad idea. Looking at Firebird development, maybe a new alternative
will show up: Queries that span multiple databases would allow you to
simply move the "hot" tables to a separate database and put that file on
a separate disk.


--
Milan Babuskov

==================================
The easiest way to import XML, CSV
and textual files into Firebird:
http://www.guacosoft.com/xmlwizard
==================================