sql server transaction logs

[Andrew S.]

I recently performed an SQL server 2000 installation. Other than
placing the program files on C: and data on D:, I saw no option to
install transaction logs in an alternate location.

What is the best practice with SQL server 2000 for location of
transaction logs? I remember that Microsoft used to take the position
that transaction logs should be placed on their own FAT partition.

[Greg D. Moore \(Strider\)]

"Andrew S." <af********@optonline.net> wrote in message
news:5b**************************@posting.google.c om...

I recently performed an SQL server 2000 installation. Other than
placing the program files on C: and data on D:, I saw no option to
install transaction logs in an alternate location.

What is the best practice with SQL server 2000 for location of
transaction logs? I remember that Microsoft used to take the position
that transaction logs should be placed on their own FAT partition.

Wow, you've been out of it for awhile. :-)

Best bet is when you create new databases is to do it by hand and place them
where you want.

[Leythos]

In article <jj********************@twister.nyroc.rr.com>,
mo****************@greenms.com says...

"Andrew S." <af********@optonline.net> wrote in message
news:5b**************************@posting.google.c om...

I recently performed an SQL server 2000 installation. Other than
placing the program files on C: and data on D:, I saw no option to
install transaction logs in an alternate location.

What is the best practice with SQL server 2000 for location of
transaction logs? I remember that Microsoft used to take the position
that transaction logs should be placed on their own FAT partition.

Wow, you've been out of it for awhile. :-)

Best bet is when you create new databases is to do it by hand and place them
where you want.

No, best method is to created them on a MIRRORED set that is comprised
of a different set of physical drives than the OS and the Database file.
The MIRROR should be defragmented before creating the transaction log
file.

You can easily change the location by doing a create script in Query
Analyzer or by using the GUI and changing the settings before creating
the database (check the tabs).
--
--
sp*********@rrohio.com
(Remove 999 to reply to me)

[Ellen K.]

A separate partition won't help nearly as much as a separate array.
I use a RAID5 array for my data and a RAID1 array (mirrored pair) for
my log.

On 26 Oct 2004 13:49:05 -0700, af********@optonline.net (Andrew S.)
wrote:

I recently performed an SQL server 2000 installation. Other than
placing the program files on C: and data on D:, I saw no option to
install transaction logs in an alternate location.

What is the best practice with SQL server 2000 for location of
transaction logs? I remember that Microsoft used to take the position
that transaction logs should be placed on their own FAT partition.