October 22, 2009 at 5:40 am
Guys I'm rolling out a SQL database server that will be used to back Sharepoint 2007. Right now I need some advice on my disk layout. I have two Dell servers that are configured a little differently in terms of storage. The principle server will be using a combination of local storage and san storage. I have to work with what I have the organization is currently all allocated on san storage it was like pulling teeth to even get what I have to work with now. My disk setup on the principle is as follows raid 1 for OS, raid 10 for logs, raid 10 fiber on san for high IO databases, raid 10 sata on san for content databases. My question in regards to the principle server is where should I place the temp db I thought about placing it on the fiber raid 10 which will be hosting my high IO Sharepoint SSP databases my only other choice is to move it to the raid 1 os partition which I’m sure you guys will be against. Now let’s talk about the mirror server it is not connected to the san it is all local 6 15k SAS drives. Now my question is the same do I put tempdb on the os partition or do I leave the os partition and use a single raid 10 for everything? Any help you can provide is much appreciated.
October 23, 2009 at 5:25 am
I would recommend only raid 10 for tempdb for principal as well as mirror. This is not a good option to use os drive for tempdb. raid 1 is mirroring only and would degrade performance if tempdb is put on raid 1.
-Lk
October 23, 2009 at 5:32 am
Lucky thanks for the reply I was leaning strongly towards the raid 10 simply because of the reasons you just stated
October 27, 2009 at 5:40 am
Since the data base are "high IO Sharepoint SSP" would it be better to use the RAID10 for log and convert it on RAID1 for log and RAID1 for tempdb?! or RAID0 for tempdb for faster access...
Doesn't the tempdb has to "fight" the IO with the Sharepoint databases and if it had it's own RAID there would be no "fight" over IO....
Pedro
October 28, 2009 at 8:59 am
PiMané can you clarify your layout let me go through what I have one more time.
My main server has 6 local sas drives that are 146gig 15k rpm I than have 2 luns on the san
one lun is a raid 10 sata the other is a raid 10 fiber. Right now I have the os on a mirror I was going to do logs on the local raid 10 and content databases on sata while high io ssp databases would be on raid 10 fiber. Now the other setup would be to use raid 1 for os raid 1 or raid 0 for tempdb this would leave raid 10 fiber on san for high io and another raid 10 sata on the san for sharepoint user content databases . I'm not sure if I'm comfortable using a raid 0 on a production system however I would look at using a raid 1 for tempd.
October 28, 2009 at 9:20 am
There are many discussions on what RAID to use on tempdb.
It depends on your application's usage of it...
If tempdb is "bombed" a lot with writes and reads, remember tempdb is a very high write database, is better to use a fast RAID, like RAID0 or RAID10 (the worst you could do is use RAID5 on tempdb).
If your application doesn't use tempdb a lot then you can go to a RAID1 solution.
Take a lot at this link from microsoft, it explain how to measure tempdb usage (http://technet.microsoft.com/en-us/library/cc966545.aspx).
The "only" problem with using RAID0 on tempdb is that if one of the disks fails your SQL Server will fail. You'll have to "restart" the system and have a new location for tempdb. Then you'll be fine...
Replace the damaged disk and "restart" the RAID0 and move the tempdb again (another restart to SQL Server).
This is why RAID10 is way better for tempdb... For high performance applications that use tempdb a lot the best solution in these day is to use SSD disks. But they are very expensive, but the best for tempdb. With SSD you can use RAID1 without any problem of access speed.
Pedro
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply