SQL 2000 Setup System Log Files?

[dball63]

I’m setting up a new SQL 2000 SP4 server. Operating system is Win2003 Server Std. SP1. With this new server I plan to migrate next month 2 user databases. When I purchased this new server I planned to do it right this time.

Drive C: RAID 1 (OS and SQL Program Files)
Drive D: RAID 1 (SQL Log files)
Drive E: RAID 5 (SQL Data files)

The server setup has gone just fine so far but now after installing MSSQL 2000 SP4, I notice the default installation places the system db’s log files in the data folder on my RAID 5 E: Drive.
My question before I can continue. Should I attempt to move the system db log files to my RAID 1 D: Drive? If so, how?
Should I just leave to system db log files where they are and put my user db logs on the Raid 1 D: Drive and have the log files on D: and E: ?
I would like to achieve the best performance possible as well as maintain accepted standard MSSQL setup for my office this time.
Can someone please help so I can continue to prepare my server for production deployment?

David
Sacramento, CA

 

[DrSql]

Depending your policy that you have allocate file locations. Just leaving your system db log files on your current location wont make a big difference. The I/O usage is so minimal, excpet tempdb. I would reccoemnd moving the tempdb log, and there are lot of articles in google how to proceed with that. But always should have a good paractice of backing up all db's.


The method that I follow is
C:\ OS
D:\ CD
E:\ MSSQL install and system dbs
F:\ All db backups

SAN

G:\ User db Data file (RAID 5)
H:\ User db Log File (RAID 5)

The purpose of using backups locally is in case the SAN crashed I have prior nights backup locally and I dont have wait to go back to the tape to recover it.
Putting the Data and Log files on the SAN also gives me that in case the Server crashed I have the MDF and LDF files on the SAN and I can recover that quickly and attach them to a new instance.
I think it varies from compnay to compnay. And we learn a lot from trial and error.
Good luck

Dr.Sql
Good Luck.

 

[mrdenny]

System databases have very few transactions running through them. You should be fine keeping the transaction logs for the system databases in the default location.

The exception is tempdb. This database's files grow and shrink quite a lot. In a system which has a very high tempdb usage you will want to put tempdb on it's own drive.

Here's an FAQ on setting up the drives for a SQL Server faq962-5747.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com