January 23, 2008 at 4:17 pm
Hi, I'm a long time developer in my first DBA role. I'm the only DBA here and am expected to be responsible for all aspects of our database servers from setup to admin to application development.
Does anyone have any good links to document describing the best practices for configuring a new server that will have SQL Server installed? I'm most interested in optimal disk configuration. Or is there not much more to know beyond having data and log files on separate arrays? It's a fairly low volume system, so I could probably completely bungle the setup and not have performance issues, but I'd still like to do it right.:)
If specifics help out, we will be installing 2000 on an HP/Compaq Proliant DL380 with 6 locally attached drives on a single controller and have 4GB of memory.
January 23, 2008 at 10:02 pm
For set up a SQL server, this may help or customize to your own environment. http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sp3sec04.mspx
A lot of best practices posts on this site. Happy searching.
January 24, 2008 at 10:13 am
Thanks Vivien, there is a lot of good information there that I will be able to use. However it doesn't really address any of my questions regarding the physical server setup. For example, there's no mention there of separating data and logs to different disks, although I'm sure I've heard somewhere that's important.
I feel pretty comfortable with tuning the server once it's setup, managing security, etc., but am looking for help with how one would build out the actual server you plan to install SQL Server on for the first time.
January 24, 2008 at 11:23 am
pauls2 (1/24/2008)
Thanks Vivien, there is a lot of good information there that I will be able to use. However it doesn't really address any of my questions regarding the physical server setup. For example, there's no mention there of separating data and logs to different disks, although I'm sure I've heard somewhere that's important.I feel pretty comfortable with tuning the server once it's setup, managing security, etc., but am looking for help with how one would build out the actual server you plan to install SQL Server on for the first time.
It really depends on the speed of disk ...
My general rule of thumb is that regardless, all the data and log files for user databases get separated into different folders for logical organization. The determining factor on whether or not they are stored on different drives is usually based on the speed of disk as well as the volume of transactional data.
If your system is at all moderately transactional, your tempdb should always be stored on a separate drive. SAN enthusiasts will beg to differ, but I always split them out regardless to as the file system. You should always have the same amount of tempdb data files to match the amount of physical CPU's (this includes Dual Cores, not hyperthreaded). If this is SQL2000, you'll also want to add the -T1118 startup flag for tempdb performance enhancements.
Again, depending on the system, I'll either leave the system data and log files in their install path, or move them to a separate drive.
In the end, it really comes down to creating your own best practices for your environment. Different servers have different requirements.
January 25, 2008 at 5:11 am
Is this maybe what you are looking for?
http://www.sql-server-performance.com/articles/audit/hardware_performance_optimization_p1.aspx
Joe
January 25, 2008 at 10:21 am
Thanks Joe. Looks like exactly what I'm looking for.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply