<<Also, I'm not sure when it changed, but the requirement for having the
log files on the same volume set as the database no longer exists unless
rollback recovery is enabled.  Perhaps, someone else on the list can
confirm this?>>


Yep. Rollback might be handy in some situations, but having an
installation that's impervious to the loss of an entire volume set is
better ;-). We keep our production databases on one user volume set, back
them up to a different volume set, and log to the backup volume set. If
the production volume set crashes, we can restore the database to the
point of the last completed transaction by rolling the backup copy
forward using the log files.

Steve