• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 57
  • Last Modified:

Sql Server disk configuration

I have a SQL server that is used for both write and read. I have a host with 8 15K drives and I need to configure the SQL server and the Databases. I have thought of 3 scenarios

Raid 1 for OS, Raid 10 (4disk) for my Data file and Raid 1 logs file
Raid 1 for OS, Raid 10 (6disk) for my Data file and logs file
Raid 10 (8disks) for everything
Any other ideas?
2 Solutions
Nitin SontakkeDeveloperCommented:
Being a business application developer, I don't have much understanding in raid configuration. Having said that, one invaluable piece of advice from SQL Server configuration is to separate disks for .mdf (data) and .ldf (log) files is a best practise from performance point of view. This may not fetch much benefit (I guess) if the drives are logical but helpful if they are physical.

Please take this with a spoonful of salt.
yo_beeDirector of Information TechnologyCommented:
I like the first layout the best.
It is best practice to separate the OS, DB's and Logs on separate logical drives.
Be that you have 8 disk your first layout is the best for performance and fault tolerance.
Option 2 is not a good practice, but can be done.
Option 3 is pretty much a NO-NO in the setup.
John TsioumprisSoftware & Systems EngineerCommented:
Some years ago when a server was ordered for SQL the vendor advised this configuration
RAID 1 OS --> 2 Disks
RAID 1 Logs --> 2 Disks
RAID 10 Data --> 4 Disks
I think i have saw a paper that also MS recommended this setup....
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

David FavorLinux/LXD/WordPress/Hosting SavantCommented:
Go with John Tsioumpris setup suggestion.

I'd likely put the OS + Logs on one disk, as once your OS starts up + loads the OS into memory, your OS disk access should be minimal... well... depending on if you have enough memory to keep from swapping... and have no other disk hog applications running that produce massive i/o thrash on the OS disk.
Information missing to say  for sure, size of available drives,
Server specs.
The log files are potentially high I/o placing them in the same spindles as the os where commonly the page file is, when the resources are need for swap, the decline in performance could be in geometric proportions.
Size of databases involved, transaction log sizes can be managed by SQL jobs for transaction log backups on a frequency.

Echo your first indicated option.
tonzur40Author Commented:
Thanks a lot I will go with option 1
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now