Move Log File Locations

I am trying to split the log and data files between two drives on a new
SQL-Server 2000 installation. I followed the instructions from the MS
article 224071 (Moving SQL Server databases to a new location with
Detach/Attach).

Unfortunalty, when I try to move the Master database, as per
instructions, access to SQL-Sever is lost;the service will never start
again. I've tried this twice after re-installing with the same results.

Anyone have any ideas as to what is going wrong?

TimDon't move the master database and log file. There is so little
activity in master that you will not gain one iota of benefit from
splitting the data and log file locations.

I am willing to bet you could put the master log file on a floppy disk
and you wouldn't notice a performance difference. The only thing read
from master (from a user perspective) is login information. Since
changes are rarely made in master, you'll get nothing from moving the
log to a separate device.|||This isn't a performance issue. We want all logs in a single directory,
and all data in a single directory (as well as separate drives) for
standardization. Performance issues related to production and tempdb
databases are the other reason.

Anyone else care to offer a solution?

Tim

joshsackett wrote:
> Don't move the master database and log file. There is so little
> activity in master that you will not gain one iota of benefit from
> splitting the data and log file locations.
> I am willing to bet you could put the master log file on a floppy
disk
> and you wouldn't notice a performance difference. The only thing read
> from master (from a user perspective) is login information. Since
> changes are rarely made in master, you'll get nothing from moving the
> log to a separate device.|||Got it - no need for a solution now :)

tim.pascoe@.cciw.ca wrote:
> This isn't a performance issue. We want all logs in a single
directory,
> and all data in a single directory (as well as separate drives) for
> standardization. Performance issues related to production and tempdb
> databases are the other reason.
> Anyone else care to offer a solution?
> Tim
>
> joshsackett wrote:
> > Don't move the master database and log file. There is so little
> > activity in master that you will not gain one iota of benefit from
> > splitting the data and log file locations.
> > I am willing to bet you could put the master log file on a floppy
> disk
> > and you wouldn't notice a performance difference. The only thing
read
> > from master (from a user perspective) is login information. Since
> > changes are rarely made in master, you'll get nothing from moving
the
> > log to a separate device.