Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
emaildgp
Starting Member
2 Posts |
 Posted - 2007-10-16 : 16:56:21
|
| I have just completed a default install of MS SQL Server 2005 x64 edition on a 1 processor Quad core, 8GB, Windows Server 2003 Standard x64 R2 machine in an Active Directory Domain. It has 2 arrays configured with 2) 36Gb drives mirrored for the OS as C: and 3) 147Gb drives in a RAID5 array as E: drive.I am simply the server guy who was asked to install SQL server for some projects in the future. The company will be bring in people to to the dev.I wanted to setup the server as best as I can and so I've been searching around for "best practices" for fresh installs.Anyone have any suggestions on things to configure/setup to improve the performance of the default install?In addition, I want to redirect the databases to the E: drive and separate them from the OS drive (C:). Does anyone have any information on doing this? I have searched and found a few articles, but thought I would ask first.It is probably noticeable that I have limited SQL configuration skills.Thanks,A simple IT guy trying to build a system right |
|
|
Zoroaster
Aged Yak Warrior
702 Posts |
Posted - 2007-10-16 : 21:02:26
|
Change the default location for data files and logs in properties when right clicking the server in SSMS. To move existing databases you can refer to: http://support.microsoft.com/kb/224071You would have been better off with more drives to separate the transaction logs from the data files, and also a different drives for the backups and tempdb. Also, RAID 10 would have been better than RAID 5.
Future guru in the making. |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2007-10-17 : 01:06:07
|
My suggestions would be:Don't use RAID5. The databases we have with RAID5 usually get corrupted when a drive goes down (because the writes are multi-page, not single page, and don't retry after failed drive is excluded from the array). Use RAID10.You need more channels. Minimum one for OS (you have that), one for Data and separate on for Logs.Ideally additional channels for TEMPDB and Backups.But that depends a bit on how "hot" the server needs to be - but its a 64-bit box, so I presume its intended to be reasonable "hot"  Damn I see that Zoroaster said that already ... OK so put me down for "+1 for what he said"  I recommend that you move SQL Server off the standard 1433 port to a port > 10000 which will prevent your average port scanner finding it and some consultant with a virus infested laptop that he's just plugged into you LAN giving you a bad day ...Kristen |
|
|
|
emaildgp
Starting Member
2 Posts |
Posted - 2007-10-17 : 08:29:21
|
| Thanks for the feedback.I'll look at adding drives for a seperate log volume.Believe it or not, this box will probably not get alot of use. It will be more of a data collection point for other system output and a few reporting dumps run at night.I just wanted to build a good machine and start learning more about SQL, from the admin side anyway.Thanks Again |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2007-10-17 : 11:58:02
|
| In that case I would be more inclined to add the extra drives, so that you get the experience of putting the TLog files on different drives and so on. There are some extra parameters needed to a restore - rather than just letting them "default" to being in the same place, and so on, that it would probably be worth experiencing.Kristen |
|
|
|
|
|
|
|
|
Fresh 2005 Install Best Practices