|
Home > Archive > MS SQL Server > August 2005 > what is best practice for setting up server computer for sql serve
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
what is best practice for setting up server computer for sql serve
|
|
|
| What is the best practice for setting up a server computer that will be
housing Sql Server 2000 Enterprise?
I will be getting a new server that will house sql server 2000 Enterprise
(along withe Visual Studio 2003 - 2005 when it comes out). This will be used
exclusively within the Company network within the confines of the firewalls.
The server computer will be using Windows 2000 Advance server OS, contains
Four 3gig processors, 32 gigs of memory and 300 gigs of harddrive space, raid
5, etc. My question is if I should have only one drive - a "C" drive for
housing the mdf files or should I partition the server computer? There will
be a lot of I/O operations and large volumes of data processing - all within
the firewalls - NO Internet. Most of the data will be comming from VB.Net/C#
apps. Some data coming in through Aspx. The goal would be best performance
and ease of maintenance.
If I were to use the server for E commerce - or just Enterprise stuff, stuff
that would be interacting on the Internet - then would I want to partition
the server computer? Here we would have an additional goal of security.
Thanks,
Rich
| |
| Mike Epprecht \(SQL MVP\) 2005-08-08, 1:23 pm |
| Hi
System Drives should be on their own partition.
Data, logs and backups should be each be on their own partitions.
And don't think partitions as being a smaller chunk of the same RAID-Volume.
Each separate raid volumes.
Don't think RAID-5, it is slow. RAID-10 is what you want.
Forget Windows 2000 AS , go Windows 2003 Enterprise Edition. 2003 has the
performance and security benefits.
Rather reduce the RAM and get more disks.
Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rich" <Rich@discussions.microsoft.com> wrote in message
news:808A43A5-0C23-46E6-BA22- 26599203254F@microso
ft.com...
> What is the best practice for setting up a server computer that will be
> housing Sql Server 2000 Enterprise?
>
> I will be getting a new server that will house sql server 2000 Enterprise
> (along withe Visual Studio 2003 - 2005 when it comes out). This will be
> used
> exclusively within the Company network within the confines of the
> firewalls.
> The server computer will be using Windows 2000 Advance server OS,
> contains
> Four 3gig processors, 32 gigs of memory and 300 gigs of harddrive space,
> raid
> 5, etc. My question is if I should have only one drive - a "C" drive for
> housing the mdf files or should I partition the server computer? There
> will
> be a lot of I/O operations and large volumes of data processing - all
> within
> the firewalls - NO Internet. Most of the data will be comming from
> VB.Net/C#
> apps. Some data coming in through Aspx. The goal would be best
> performance
> and ease of maintenance.
>
> If I were to use the server for E commerce - or just Enterprise stuff,
> stuff
> that would be interacting on the Internet - then would I want to partition
> the server computer? Here we would have an additional goal of security.
>
> Thanks,
> Rich
|
|
|
|
|