Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2005
»
Administering
»
RAID 1 vs. RAID 10
57 posts, Page 1 of 6
1
2
3
4
5
»
»»
RAID 1 vs. RAID 10
Rate Topic
Display Mode
Topic Options
Author
Message
Kendal Van Dyke
Kendal Van Dyke
Posted Tuesday, December 23, 2008 12:43 PM
Old Hand
Group: General Forum Members
Last Login: Thursday, May 16, 2013 2:58 PM
Points: 361,
Visits: 780
Lots of great articles on the intertubez about disk alignment and RAID configurations but I haven't found an answer (or a good way to test, and yes I know about SQLIO) for a simple scenario:
Suppose I have 4 local physical disks available to me and I'm going to create an OLTP DB (for the sake of arguing let's say we're 50\50 on reads and writes, or otherwise average usage). Here are two scenarios that I would consider:
1) Two RAID 1 drives. Create the DB with two data files, i.e. one data file on each drive
2) One RAID 10 drive. Create the DB with one single data file
In the RAID 1 scenario (as I understand it) SQL will round robin writes between the two data files, thus creating a software equivalent of striping. RAID 10, on the other hand, handles the striping at a hardware level. Those differences aside, I haven't found a good technical explanation - or numbers to back it - for what's happening under the covers that would make me believe one option is better than the other.
So which of these two scenarios is more ideal and why?
Kendal Van Dyke
http://kendalvandyke.blogspot.com/
Post #624961
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Tuesday, December 23, 2008 1:06 PM
SSC-Dedicated
Group: Administrators
Last Login: Yesterday @ 2:54 PM
Points: 31,410,
Visits: 13,726
I would argue Raid 10 for one reason. You're not 100% sure of the usage and balance among the drives and with 2 R1s, you can run out of space on one, have space on the other. With one large R10, it gets handled and you get to use all the space.
Other than that, I'm not sure there's a great technical argument for R1 v R10.
Follow me on Twitter:
@way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
Post #624975
RBarryYoung
RBarryYoung
Posted Tuesday, December 23, 2008 2:13 PM
SSCrazy Eights
Group: General Forum Members
Last Login: Saturday, May 04, 2013 11:13 AM
Points: 9,855,
Visits: 9,374
You should worry about your Log file before you add a second data file.
-- RBarryYoung
,
(302)375-0451
blog:
MovingSQL.com
, Twitter:
@RBarryYoung
Proactive
Performance Solutions, Inc.
"Performance is our middle name."
Post #625034
Kendal Van Dyke
Kendal Van Dyke
Posted Tuesday, December 23, 2008 2:19 PM
Old Hand
Group: General Forum Members
Last Login: Thursday, May 16, 2013 2:58 PM
Points: 361,
Visits: 780
RBarryYoung (12/23/2008)
You should worry about your Log file before you add a second data file.
Ummm....thanks....but kinda not the point of the post. I'm looking for technical reasons why a single data file on RAID 10 is better than two data files on two RAID 1's.
But FWIW I'll stick my log files on a different drive than my data files altogether.
Kendal Van Dyke
http://kendalvandyke.blogspot.com/
Post #625040
matt stockham
matt stockham
Posted Tuesday, December 23, 2008 9:52 PM
Right there with Babe
Group: General Forum Members
Last Login: Thursday, March 14, 2013 10:22 AM
Points: 750,
Visits: 2,937
I doubt that there is much difference from a performance standpoint ... the raid 1 scenario would presumably require a tiny increase in system resources. Raid 10 would appear to be a little easier to manage in as much as you would be dealing with one file rather than two. If I remember correctly, fragmentation statistics aren't accurate for multiple files either.
The above all assumes that the 2 files are across one filegroup (as that would use the proportional fill algorithm) - if one were to split the database into two filegroups (one file per filegroup) then there are other potential advantages from the raid 1 scenario .... filegroup backups, partitioning etc etc.
Post #625162
Mike John
Mike John
Posted Wednesday, December 24, 2008 2:19 AM
SSCrazy
Group: General Forum Members
Last Login: Yesterday @ 3:31 AM
Points: 2,637,
Visits: 4,545
Another possible implication of two raid 1s would be if they were the same filegroup, with a massive table that was frequently being scanned. If I remember rightly in that situation (table scan, table on more than 1 file group) SQL Server will initiate multiple threads (one per file) and run the scans in parallel.
Mike
Post #625240
RBarryYoung
RBarryYoung
Posted Wednesday, December 24, 2008 8:19 AM
SSCrazy Eights
Group: General Forum Members
Last Login: Saturday, May 04, 2013 11:13 AM
Points: 9,855,
Visits: 9,374
kendal.vandyke (12/23/2008)
I'm looking for technical reasons why a single data file on RAID 10 is better than two data files on two RAID 1's.
Ah, I see, I misunderstood the intent of your question. Sorry...
-- RBarryYoung
,
(302)375-0451
blog:
MovingSQL.com
, Twitter:
@RBarryYoung
Proactive
Performance Solutions, Inc.
"Performance is our middle name."
Post #625408
Kendal Van Dyke
Kendal Van Dyke
Posted Wednesday, December 24, 2008 8:30 AM
Old Hand
Group: General Forum Members
Last Login: Thursday, May 16, 2013 2:58 PM
Points: 361,
Visits: 780
Ah, I see, I misunderstood the intent of your question. Sorry...
No apologies necessary! :)
Kendal Van Dyke
http://kendalvandyke.blogspot.com/
Post #625417
Perry Whittle
Perry Whittle
Posted Wednesday, December 24, 2008 12:49 PM
SSCertifiable
Group: General Forum Members
Last Login: Yesterday @ 9:47 AM
Points: 5,201,
Visits: 11,151
i would say the RAID 10 array is best as it offers the best performance and fault tolerance combined into one package. The downside of RAID 10 is the disk cost (no of disks required)
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs"
Post #625549
Kendal Van Dyke
Kendal Van Dyke
Posted Wednesday, December 24, 2008 3:37 PM
Old Hand
Group: General Forum Members
Last Login: Thursday, May 16, 2013 2:58 PM
Points: 361,
Visits: 780
i would say the RAID 10 array is best as it offers the best performance and fault tolerance combined into one package. The downside of RAID 10 is the disk cost (no of disks required)
Maybe the question was misunderstood. I proposed two scenarios for how to configure 4 disks to hold data. A single RAID 10 with 4 disks is just as fault tolerant as two RAID 1 drives - each can lose 1 disk per pair. Likewise the disk cost is the same in the question I asked.
As for performance, I'm looking for something solid to show that RAID 10 would be better than RAID 1 or vice versa. I was really hoping someone knew enough about what's going on under the covers (e.g. IO paths, threads, etc.) to make it clear.
Kendal Van Dyke
http://kendalvandyke.blogspot.com/
Post #625589
« Prev Topic
|
Next Topic »
57 posts, Page 1 of 6
1
2
3
4
5
»
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.