I am going to buy a new server that will be running Windows 2003 Server,
Exchange 2003 & SQL 2000. I was looking at a server with dual Xeon 3.6Ghz
processors with 2GB RAM & RAID 5 but I was told that I should use RAID 1
instead of RAID 5. Is this true that RAID 1 will work better with this setup
or am I being mis-informed and why would RAID 1 be better than RAID 5?
How about the processor's and RAM?
Thanks,
ScottWell you need to keep the following in mind:
1. One I/O per logical read is required on all RAIDS (0,1,10,5)
2. For each logical write, the following applies:
RAID 1: 2 I/Os.
RAID 5: 4 I/Os.
Based on the analysis of requirements that you have done (or should do!),
you can decide what is the most appropriate. Typically, a database
transaction log is put on a RAID 1 since 95%+ of all transactions of a
transaction log are WRITEs and you do not want to go for a RAID 5 if
possible. Cost wise RAID 1 will cost you more. Now, if you should have
Exchange and SQL on the same box is another topic but ultimately it depends
on the load you are expecting on the server. I personally don't like running
anything else on a SQL Server machine. Also keep in mind that SQL Server 200
0
Standard will not use more than 2 GBs of ram.
The decision you will make can be critical for your business and I suggest
you read on Capacity planning in SQL Server Administrator Companion
(MicrosoftPress).
Sasan
"Scott A" wrote:
> I am going to buy a new server that will be running Windows 2003 Server,
> Exchange 2003 & SQL 2000. I was looking at a server with dual Xeon 3.6Ghz
> processors with 2GB RAM & RAID 5 but I was told that I should use RAID 1
> instead of RAID 5. Is this true that RAID 1 will work better with this set
up
> or am I being mis-informed and why would RAID 1 be better than RAID 5?
> How about the processor's and RAM?
> Thanks,
> Scott|||Thanks Susan. I forgot to add that we have about 70 users on Exchange and ou
r
new SQL database will have 5-10 users on at any given time. Does this make a
difference at all?
Thanks,
Scott
"Sasan Saidi" wrote:
[vbcol=seagreen]
> Well you need to keep the following in mind:
> 1. One I/O per logical read is required on all RAIDS (0,1,10,5)
> 2. For each logical write, the following applies:
> RAID 1: 2 I/Os.
> RAID 5: 4 I/Os.
> Based on the analysis of requirements that you have done (or should do!),
> you can decide what is the most appropriate. Typically, a database
> transaction log is put on a RAID 1 since 95%+ of all transactions of a
> transaction log are WRITEs and you do not want to go for a RAID 5 if
> possible. Cost wise RAID 1 will cost you more. Now, if you should have
> Exchange and SQL on the same box is another topic but ultimately it depend
s
> on the load you are expecting on the server. I personally don't like runni
ng
> anything else on a SQL Server machine. Also keep in mind that SQL Server 2
000
> Standard will not use more than 2 GBs of ram.
> The decision you will make can be critical for your business and I suggest
> you read on Capacity planning in SQL Server Administrator Companion
> (MicrosoftPress).
> Sasan
>
> "Scott A" wrote:
>
Showing posts with label xeon. Show all posts
Showing posts with label xeon. Show all posts
Monday, March 12, 2012
Hardware requirements
I am going to buy a new server that will be running Windows 2003 Server,
Exchange 2003 & SQL 2000. I was looking at a server with dual Xeon 3.6Ghz
processors with 2GB RAM & RAID 5 but I was told that I should use RAID 1
instead of RAID 5. Is this true that RAID 1 will work better with this setup
or am I being mis-informed and why would RAID 1 be better than RAID 5?
How about the processor's and RAM?
Thanks,
Scott
Well you need to keep the following in mind:
1. One I/O per logical read is required on all RAIDS (0,1,10,5)
2. For each logical write, the following applies:
RAID 1: 2 I/Os.
RAID 5: 4 I/Os.
Based on the analysis of requirements that you have done (or should do!),
you can decide what is the most appropriate. Typically, a database
transaction log is put on a RAID 1 since 95%+ of all transactions of a
transaction log are WRITEs and you do not want to go for a RAID 5 if
possible. Cost wise RAID 1 will cost you more. Now, if you should have
Exchange and SQL on the same box is another topic but ultimately it depends
on the load you are expecting on the server. I personally don't like running
anything else on a SQL Server machine. Also keep in mind that SQL Server 2000
Standard will not use more than 2 GBs of ram.
The decision you will make can be critical for your business and I suggest
you read on Capacity planning in SQL Server Administrator Companion
(MicrosoftPress).
Sasan
"Scott A" wrote:
> I am going to buy a new server that will be running Windows 2003 Server,
> Exchange 2003 & SQL 2000. I was looking at a server with dual Xeon 3.6Ghz
> processors with 2GB RAM & RAID 5 but I was told that I should use RAID 1
> instead of RAID 5. Is this true that RAID 1 will work better with this setup
> or am I being mis-informed and why would RAID 1 be better than RAID 5?
> How about the processor's and RAM?
> Thanks,
> Scott
|||Thanks Susan. I forgot to add that we have about 70 users on Exchange and our
new SQL database will have 5-10 users on at any given time. Does this make a
difference at all?
Thanks,
Scott
"Sasan Saidi" wrote:
[vbcol=seagreen]
> Well you need to keep the following in mind:
> 1. One I/O per logical read is required on all RAIDS (0,1,10,5)
> 2. For each logical write, the following applies:
> RAID 1: 2 I/Os.
> RAID 5: 4 I/Os.
> Based on the analysis of requirements that you have done (or should do!),
> you can decide what is the most appropriate. Typically, a database
> transaction log is put on a RAID 1 since 95%+ of all transactions of a
> transaction log are WRITEs and you do not want to go for a RAID 5 if
> possible. Cost wise RAID 1 will cost you more. Now, if you should have
> Exchange and SQL on the same box is another topic but ultimately it depends
> on the load you are expecting on the server. I personally don't like running
> anything else on a SQL Server machine. Also keep in mind that SQL Server 2000
> Standard will not use more than 2 GBs of ram.
> The decision you will make can be critical for your business and I suggest
> you read on Capacity planning in SQL Server Administrator Companion
> (MicrosoftPress).
> Sasan
>
> "Scott A" wrote:
Exchange 2003 & SQL 2000. I was looking at a server with dual Xeon 3.6Ghz
processors with 2GB RAM & RAID 5 but I was told that I should use RAID 1
instead of RAID 5. Is this true that RAID 1 will work better with this setup
or am I being mis-informed and why would RAID 1 be better than RAID 5?
How about the processor's and RAM?
Thanks,
Scott
Well you need to keep the following in mind:
1. One I/O per logical read is required on all RAIDS (0,1,10,5)
2. For each logical write, the following applies:
RAID 1: 2 I/Os.
RAID 5: 4 I/Os.
Based on the analysis of requirements that you have done (or should do!),
you can decide what is the most appropriate. Typically, a database
transaction log is put on a RAID 1 since 95%+ of all transactions of a
transaction log are WRITEs and you do not want to go for a RAID 5 if
possible. Cost wise RAID 1 will cost you more. Now, if you should have
Exchange and SQL on the same box is another topic but ultimately it depends
on the load you are expecting on the server. I personally don't like running
anything else on a SQL Server machine. Also keep in mind that SQL Server 2000
Standard will not use more than 2 GBs of ram.
The decision you will make can be critical for your business and I suggest
you read on Capacity planning in SQL Server Administrator Companion
(MicrosoftPress).
Sasan
"Scott A" wrote:
> I am going to buy a new server that will be running Windows 2003 Server,
> Exchange 2003 & SQL 2000. I was looking at a server with dual Xeon 3.6Ghz
> processors with 2GB RAM & RAID 5 but I was told that I should use RAID 1
> instead of RAID 5. Is this true that RAID 1 will work better with this setup
> or am I being mis-informed and why would RAID 1 be better than RAID 5?
> How about the processor's and RAM?
> Thanks,
> Scott
|||Thanks Susan. I forgot to add that we have about 70 users on Exchange and our
new SQL database will have 5-10 users on at any given time. Does this make a
difference at all?
Thanks,
Scott
"Sasan Saidi" wrote:
[vbcol=seagreen]
> Well you need to keep the following in mind:
> 1. One I/O per logical read is required on all RAIDS (0,1,10,5)
> 2. For each logical write, the following applies:
> RAID 1: 2 I/Os.
> RAID 5: 4 I/Os.
> Based on the analysis of requirements that you have done (or should do!),
> you can decide what is the most appropriate. Typically, a database
> transaction log is put on a RAID 1 since 95%+ of all transactions of a
> transaction log are WRITEs and you do not want to go for a RAID 5 if
> possible. Cost wise RAID 1 will cost you more. Now, if you should have
> Exchange and SQL on the same box is another topic but ultimately it depends
> on the load you are expecting on the server. I personally don't like running
> anything else on a SQL Server machine. Also keep in mind that SQL Server 2000
> Standard will not use more than 2 GBs of ram.
> The decision you will make can be critical for your business and I suggest
> you read on Capacity planning in SQL Server Administrator Companion
> (MicrosoftPress).
> Sasan
>
> "Scott A" wrote:
Hardware requirements
I am going to buy a new server that will be running Windows 2003 Server,
Exchange 2003 & SQL 2000. I was looking at a server with dual Xeon 3.6Ghz
processors with 2GB RAM & RAID 5 but I was told that I should use RAID 1
instead of RAID 5. Is this true that RAID 1 will work better with this setup
or am I being mis-informed and why would RAID 1 be better than RAID 5?
How about the processor's and RAM?
Thanks,
ScottWell you need to keep the following in mind:
1. One I/O per logical read is required on all RAIDS (0,1,10,5)
2. For each logical write, the following applies:
RAID 1: 2 I/Os.
RAID 5: 4 I/Os.
Based on the analysis of requirements that you have done (or should do!),
you can decide what is the most appropriate. Typically, a database
transaction log is put on a RAID 1 since 95%+ of all transactions of a
transaction log are WRITEs and you do not want to go for a RAID 5 if
possible. Cost wise RAID 1 will cost you more. Now, if you should have
Exchange and SQL on the same box is another topic but ultimately it depends
on the load you are expecting on the server. I personally don't like running
anything else on a SQL Server machine. Also keep in mind that SQL Server 2000
Standard will not use more than 2 GBs of ram.
The decision you will make can be critical for your business and I suggest
you read on Capacity planning in SQL Server Administrator Companion
(MicrosoftPress).
Sasan
"Scott A" wrote:
> I am going to buy a new server that will be running Windows 2003 Server,
> Exchange 2003 & SQL 2000. I was looking at a server with dual Xeon 3.6Ghz
> processors with 2GB RAM & RAID 5 but I was told that I should use RAID 1
> instead of RAID 5. Is this true that RAID 1 will work better with this setup
> or am I being mis-informed and why would RAID 1 be better than RAID 5?
> How about the processor's and RAM?
> Thanks,
> Scott|||Thanks Susan. I forgot to add that we have about 70 users on Exchange and our
new SQL database will have 5-10 users on at any given time. Does this make a
difference at all?
Thanks,
Scott
"Sasan Saidi" wrote:
> Well you need to keep the following in mind:
> 1. One I/O per logical read is required on all RAIDS (0,1,10,5)
> 2. For each logical write, the following applies:
> RAID 1: 2 I/Os.
> RAID 5: 4 I/Os.
> Based on the analysis of requirements that you have done (or should do!),
> you can decide what is the most appropriate. Typically, a database
> transaction log is put on a RAID 1 since 95%+ of all transactions of a
> transaction log are WRITEs and you do not want to go for a RAID 5 if
> possible. Cost wise RAID 1 will cost you more. Now, if you should have
> Exchange and SQL on the same box is another topic but ultimately it depends
> on the load you are expecting on the server. I personally don't like running
> anything else on a SQL Server machine. Also keep in mind that SQL Server 2000
> Standard will not use more than 2 GBs of ram.
> The decision you will make can be critical for your business and I suggest
> you read on Capacity planning in SQL Server Administrator Companion
> (MicrosoftPress).
> Sasan
>
> "Scott A" wrote:
> > I am going to buy a new server that will be running Windows 2003 Server,
> > Exchange 2003 & SQL 2000. I was looking at a server with dual Xeon 3.6Ghz
> > processors with 2GB RAM & RAID 5 but I was told that I should use RAID 1
> > instead of RAID 5. Is this true that RAID 1 will work better with this setup
> > or am I being mis-informed and why would RAID 1 be better than RAID 5?
> >
> > How about the processor's and RAM?
> >
> > Thanks,
> > Scott
Exchange 2003 & SQL 2000. I was looking at a server with dual Xeon 3.6Ghz
processors with 2GB RAM & RAID 5 but I was told that I should use RAID 1
instead of RAID 5. Is this true that RAID 1 will work better with this setup
or am I being mis-informed and why would RAID 1 be better than RAID 5?
How about the processor's and RAM?
Thanks,
ScottWell you need to keep the following in mind:
1. One I/O per logical read is required on all RAIDS (0,1,10,5)
2. For each logical write, the following applies:
RAID 1: 2 I/Os.
RAID 5: 4 I/Os.
Based on the analysis of requirements that you have done (or should do!),
you can decide what is the most appropriate. Typically, a database
transaction log is put on a RAID 1 since 95%+ of all transactions of a
transaction log are WRITEs and you do not want to go for a RAID 5 if
possible. Cost wise RAID 1 will cost you more. Now, if you should have
Exchange and SQL on the same box is another topic but ultimately it depends
on the load you are expecting on the server. I personally don't like running
anything else on a SQL Server machine. Also keep in mind that SQL Server 2000
Standard will not use more than 2 GBs of ram.
The decision you will make can be critical for your business and I suggest
you read on Capacity planning in SQL Server Administrator Companion
(MicrosoftPress).
Sasan
"Scott A" wrote:
> I am going to buy a new server that will be running Windows 2003 Server,
> Exchange 2003 & SQL 2000. I was looking at a server with dual Xeon 3.6Ghz
> processors with 2GB RAM & RAID 5 but I was told that I should use RAID 1
> instead of RAID 5. Is this true that RAID 1 will work better with this setup
> or am I being mis-informed and why would RAID 1 be better than RAID 5?
> How about the processor's and RAM?
> Thanks,
> Scott|||Thanks Susan. I forgot to add that we have about 70 users on Exchange and our
new SQL database will have 5-10 users on at any given time. Does this make a
difference at all?
Thanks,
Scott
"Sasan Saidi" wrote:
> Well you need to keep the following in mind:
> 1. One I/O per logical read is required on all RAIDS (0,1,10,5)
> 2. For each logical write, the following applies:
> RAID 1: 2 I/Os.
> RAID 5: 4 I/Os.
> Based on the analysis of requirements that you have done (or should do!),
> you can decide what is the most appropriate. Typically, a database
> transaction log is put on a RAID 1 since 95%+ of all transactions of a
> transaction log are WRITEs and you do not want to go for a RAID 5 if
> possible. Cost wise RAID 1 will cost you more. Now, if you should have
> Exchange and SQL on the same box is another topic but ultimately it depends
> on the load you are expecting on the server. I personally don't like running
> anything else on a SQL Server machine. Also keep in mind that SQL Server 2000
> Standard will not use more than 2 GBs of ram.
> The decision you will make can be critical for your business and I suggest
> you read on Capacity planning in SQL Server Administrator Companion
> (MicrosoftPress).
> Sasan
>
> "Scott A" wrote:
> > I am going to buy a new server that will be running Windows 2003 Server,
> > Exchange 2003 & SQL 2000. I was looking at a server with dual Xeon 3.6Ghz
> > processors with 2GB RAM & RAID 5 but I was told that I should use RAID 1
> > instead of RAID 5. Is this true that RAID 1 will work better with this setup
> > or am I being mis-informed and why would RAID 1 be better than RAID 5?
> >
> > How about the processor's and RAM?
> >
> > Thanks,
> > Scott
Hardware Recommendation
Hello,
I plan to run Microsoft CRM, Navision SQL, and Project Server off the
same SQL box. What would you recommend hardware wise?
Dual 2.8 Xeon? How much RAM? 2GB? 4GB?
Thanks in advance
First, put as much memory as you can afford in the box. Be aware that
anything over 4GB will require Enterprise Edition to take advantage of the
extra RAM. Dual Procs are a minimum. Go with procs with more cache rather
than faster procs, but only by 300-500 MHz. Then we geet to the disk
system. Definitely separate your SQL logs and data onto different spindles.
RAID 1 or 1+0 for logs will improve performance significantly. RAID 1+0 for
data if you can afford it, RAID5 otherwise, but it will impact performance.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"CB" <chadb@.dentistryonline.com> wrote in message
news:esoMsGvMEHA.3096@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I plan to run Microsoft CRM, Navision SQL, and Project Server off the
> same SQL box. What would you recommend hardware wise?
> Dual 2.8 Xeon? How much RAM? 2GB? 4GB?
> Thanks in advance
>
I plan to run Microsoft CRM, Navision SQL, and Project Server off the
same SQL box. What would you recommend hardware wise?
Dual 2.8 Xeon? How much RAM? 2GB? 4GB?
Thanks in advance
First, put as much memory as you can afford in the box. Be aware that
anything over 4GB will require Enterprise Edition to take advantage of the
extra RAM. Dual Procs are a minimum. Go with procs with more cache rather
than faster procs, but only by 300-500 MHz. Then we geet to the disk
system. Definitely separate your SQL logs and data onto different spindles.
RAID 1 or 1+0 for logs will improve performance significantly. RAID 1+0 for
data if you can afford it, RAID5 otherwise, but it will impact performance.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"CB" <chadb@.dentistryonline.com> wrote in message
news:esoMsGvMEHA.3096@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I plan to run Microsoft CRM, Navision SQL, and Project Server off the
> same SQL box. What would you recommend hardware wise?
> Dual 2.8 Xeon? How much RAM? 2GB? 4GB?
> Thanks in advance
>
Hardware Recommendation
Hello,
I plan to run Microsoft CRM, Navision SQL, and Project Server off the
same SQL box. What would you recommend hardware wise?
Dual 2.8 Xeon? How much RAM? 2GB? 4GB?
Thanks in advanceFirst, put as much memory as you can afford in the box. Be aware that
anything over 4GB will require Enterprise Edition to take advantage of the
extra RAM. Dual Procs are a minimum. Go with procs with more cache rather
than faster procs, but only by 300-500 MHz. Then we geet to the disk
system. Definitely separate your SQL logs and data onto different spindles.
RAID 1 or 1+0 for logs will improve performance significantly. RAID 1+0 for
data if you can afford it, RAID5 otherwise, but it will impact performance.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"CB" <chadb@.dentistryonline.com> wrote in message
news:esoMsGvMEHA.3096@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I plan to run Microsoft CRM, Navision SQL, and Project Server off the
> same SQL box. What would you recommend hardware wise?
> Dual 2.8 Xeon? How much RAM? 2GB? 4GB?
> Thanks in advance
>
I plan to run Microsoft CRM, Navision SQL, and Project Server off the
same SQL box. What would you recommend hardware wise?
Dual 2.8 Xeon? How much RAM? 2GB? 4GB?
Thanks in advanceFirst, put as much memory as you can afford in the box. Be aware that
anything over 4GB will require Enterprise Edition to take advantage of the
extra RAM. Dual Procs are a minimum. Go with procs with more cache rather
than faster procs, but only by 300-500 MHz. Then we geet to the disk
system. Definitely separate your SQL logs and data onto different spindles.
RAID 1 or 1+0 for logs will improve performance significantly. RAID 1+0 for
data if you can afford it, RAID5 otherwise, but it will impact performance.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"CB" <chadb@.dentistryonline.com> wrote in message
news:esoMsGvMEHA.3096@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I plan to run Microsoft CRM, Navision SQL, and Project Server off the
> same SQL box. What would you recommend hardware wise?
> Dual 2.8 Xeon? How much RAM? 2GB? 4GB?
> Thanks in advance
>
Hardware Recommendation
Hello,
I plan to run Microsoft CRM, Navision SQL, and Project Server off the
same SQL box. What would you recommend hardware wise?
Dual 2.8 Xeon? How much RAM? 2GB? 4GB?
Thanks in advanceFirst, put as much memory as you can afford in the box. Be aware that
anything over 4GB will require Enterprise Edition to take advantage of the
extra RAM. Dual Procs are a minimum. Go with procs with more cache rather
than faster procs, but only by 300-500 MHz. Then we geet to the disk
system. Definitely separate your SQL logs and data onto different spindles.
RAID 1 or 1+0 for logs will improve performance significantly. RAID 1+0 for
data if you can afford it, RAID5 otherwise, but it will impact performance.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"CB" <chadb@.dentistryonline.com> wrote in message
news:esoMsGvMEHA.3096@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I plan to run Microsoft CRM, Navision SQL, and Project Server off the
> same SQL box. What would you recommend hardware wise?
> Dual 2.8 Xeon? How much RAM? 2GB? 4GB?
> Thanks in advance
>
I plan to run Microsoft CRM, Navision SQL, and Project Server off the
same SQL box. What would you recommend hardware wise?
Dual 2.8 Xeon? How much RAM? 2GB? 4GB?
Thanks in advanceFirst, put as much memory as you can afford in the box. Be aware that
anything over 4GB will require Enterprise Edition to take advantage of the
extra RAM. Dual Procs are a minimum. Go with procs with more cache rather
than faster procs, but only by 300-500 MHz. Then we geet to the disk
system. Definitely separate your SQL logs and data onto different spindles.
RAID 1 or 1+0 for logs will improve performance significantly. RAID 1+0 for
data if you can afford it, RAID5 otherwise, but it will impact performance.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"CB" <chadb@.dentistryonline.com> wrote in message
news:esoMsGvMEHA.3096@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I plan to run Microsoft CRM, Navision SQL, and Project Server off the
> same SQL box. What would you recommend hardware wise?
> Dual 2.8 Xeon? How much RAM? 2GB? 4GB?
> Thanks in advance
>
Subscribe to:
Posts (Atom)