Re: Building New Server - What RAID should be used and how to divi

It is a transactional database that is also used for reporting. It also
doesn't have the best designed.

"Ekrem Önsoy" wrote:

I agree with Andrew from the start to the end of his message.

He also told you some from Best Practices, however, best practices may not
apply your environment. We do not even know if your databases is OLAP or
OLTP, I think it would be right to say "You should determine this first of
all"

--
Ekrem Önsoy



"Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx> wrote in message
news:%23a6X1rsCIHA.1188@xxxxxxxxxxxxxxxxxxxxxxx
Don't take this the wrong way but why is he asking you to come up with
something that you admit you know nothing about? There are a lot of
factors to consider and we don't have enough information to give you the
best answer for your situation. He should contract someone who does know
how to get to the bottom of this so that you make the correct decision and
do it right the first time. But some basics are:

Don't confuse a Logical drive with a Physical drive or array. Creating
multiple Logical drives such as C:, D: & E: on one physical array does
nothing for performance but gives false impressions of files residing on
different drives.

Never use Raid 0 if you are concerned with data loss.

Raid 5 should only be considered if there is mostly Read activity or very
low write activity. Raid 10 is a better choice for data files.

RAID 1 is a starting point for Log files. Heavy systems may need Raid 10

Never mix Log files with Data files. You can get away with adding multiple
log files to a single Raid 1 but never put data files on it.

Use a Raid 1 for the OS and sql binaries. If the usage is low enough you
can usually get by with placing the log files on this array as well.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"lcerni" <lcerni@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A36B636F-D433-40E6-8EF6-B70AFB929907@xxxxxxxxxxxxxxxx
Building New Server - What RAID should be used and how to divide the
files
among the disk drives?

Ok. I admit I am completely confused. I am being asked to research for
a
new server. My manager wants to know how many drives are needed
depending on
the RAID. Currently our organization is using RAID-5. However, I am not
sure how to split up the data files and transactional logs.

Should the master, msdb, model data files be on drive e?
Should the master, msdb, model log files be on drive g?
Or should each database data file be on its own drive and each database
log
file on another drive?
Or should all the data files be on one drive and the log files on a
second
drive?
What about tempdb? Should the tempdb data file be on one drive separate
from the others and its log file on a drive separate from the other log
files? Also I think that I read that tempdb should be on RAID 0; that it
can
be on a separate RAID from the other files? Is this true?

This is an example that I have put together. I don't know how
correct/not
correct it is though.
c: operating system ?
d: data files for all user databases ?
e: data files for all system databases ?
f: log files for all user databases ?
g: log files for all system databases ?
h: tempdb data file RAID 0
i: tempdb log file RAID 0

He made a remark that he thought that we might need about 16 drives? I
am
not sure I understand the relationship between the drives and RAID. I am
wondering if I am misunderstanding him.

How do most people have their servers set up?

Are there recommendations which files should be what RAID?



.

Relevant Pages

  • Re: SQL 2005 Best Practice vs SQL 2000: Application Files Separate from data (and log) files
    ... You'll not be using most of the system databases intensively so you don't need to seperate them, I mean locating them on different physical disks. ... If it's being used intensively in your environment then you should locate it's log and data files on different physical disks. ... For this question you must understand the reason why we should seperate data and log files. ... Of course these drives must be physically seperated so that you'll gain performance benefits. ...
    (microsoft.public.sqlserver.setup)
  • Re: tempdb on C drive?
    ... performance from having the tempdb data files, User db data files and Log ... files all on different physical drives or drive arrays. ... While adding more log files to the log drive array decreases the ...
    (microsoft.public.sqlserver.setup)
  • Re: Installing SQL Server 2005 on Windows 2003 Server (RAID 5) - need advice
    ... available disks and set up I can put the data files on D: ... on RAID 5 which has a greater read performance ... and put the .ldf files (Log files, by their nature, are mostly written ...
    (microsoft.public.sqlserver.setup)
  • Re: Building New Server - What RAID should be used and how to divide t
    ... Creating multiple Logical drives such as C:, D: & E: on one physical array does nothing for performance but gives false impressions of files residing on different drives. ... Raid 5 should only be considered if there is mostly Read activity or very low write activity. ... Raid 10 is a better choice for data files. ... RAID 1 is a starting point for Log files. ...
    (microsoft.public.sqlserver.setup)
  • Re: Building New Server - What RAID should be used and how to divide t
    ... Creating multiple Logical drives such as C:, D: & E: on one physical array does nothing for performance but gives false impressions of files residing on different drives. ... Raid 5 should only be considered if there is mostly Read activity or very low write activity. ... Raid 10 is a better choice for data files. ... RAID 1 is a starting point for Log files. ...
    (microsoft.public.sqlserver.setup)