March 24, 2009 at 9:27 am
We're in the process of planning out our SQL Server 2008 box for a SharePoint 2007 deployment. We're going to be using local disks and I'm not sure how best to structure the storage. Here are the parameters:
The server is an HP DL380 G5, 12GB RAM and 8 drive slots. We currently have 2 x 146GB 10k RPM disks available to use. We can also get 72GB 15k RPM drives or 300GB 10k RPM drives. My thought in terms of partitions and disks was:
C: RAID1 72 GB (2 x 72GB @ 15k RPM) – OS, pagefile, SQL Binaries and SQL tempdb.
D: RAID5 900GB (4 x 300GB @ 10k RPM) or RAID5 216GB (4 x 72GB @ 15k RPM) – SQL data files.
L: RAID1 72GB (2 x 72GB @ 15k RPM) – SQL log files.
Backups would go to a network share which would be picked up with our regular backup policy (per Brent Ozar http://www.brentozar.com/archive/2007/10/backing-up-sql-server-my-own-mediocre-practices/[/url]).
For 12GB RAM, I'm thinking a default install of Win Server 2k8 will have a big enough page file but I've never worked in 2k8. This is a smallish SharePoint implementation. Under 500 external users (mostly readers) and 50 internal users (50/50 readers/writers).
I estimate that the C partition would have about 28GB left after all is said and done which is ok. I don't think the logs are going to be too big but it is tough to say. 900GB seems overkill in terms of space but I know SharePoint content databases can get big quickly. My other concern is that I've heard SharePoint can be tempdb intensive.
I got spoiled working with SANs for so long. I'm not sure the best way to balance the tradeoffs with only a few disks. Any suggestions?
Thanks,
Rob
March 25, 2009 at 1:37 am
Rob Symonds (3/24/2009)
C: RAID1 72 GB (2 x 72GB @ 15k RPM) – OS, pagefile, SQL Binaries and SQL tempdb.D: RAID5 900GB (4 x 300GB @ 10k RPM) or RAID5 216GB (4 x 72GB @ 15k RPM) – SQL data files.
L: RAID1 72GB (2 x 72GB @ 15k RPM) – SQL log files.
MOSS can be very resource intensive specially when building indexes and such. I don't mange MOSS environment but I manage SQL with large MOSS configuration.
Few things you should know about MOSS DB ...
1) Microsoft doesn't recommend you create/alter any indexes in db (not supported).
2) Database max size should not exceed 100GB (I think I'll try to hunt my documents I got from the MOSS Support Engineer tomorrow, when I get to work).
3) When working in MOSS DB the Log files can grow quickly on the admin site, in some cases when creating new db and upgrading from old I have seen the T-Log file grow by 20-50gb in one day.
For your raid configuration I would recommend ...
C: Raid 1 - 72G x2
D: Raid 10 - 300G x4 (for high read/write performance)
E: Raid 1 - 72G x2
+: Your data files get best performance, your tempdb and ldf files get their own I/O channels.
-: You lose about 300G on Drive D from your original plan.
But since you said you don't expect heavy write activity with in MOSS dbs them self maybe you want to look at the following to give your Temp DB high performance of the 15K drives:
C: Raid 10 - 72G x4
D: Raid 1 - 300G x2
E: Raid 1 - 72G x2
+: Your give your tempdb extra boost with the Raid 10 configuration to allow for more excessive usage of tempdb. You gain another 72GB on C so you tempdb has more room to grow.
-: You lose about 600G on Drive D from your original plan.
Temp DB can be used by SQL server a lot, not just MOSS because SQL Server uses it for versioning, logical tables, workspace, etc.
My experiences are with MOSS 2007 and SQL 2005 however... but I would expect similar results...
Thanks.
Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
Microsoft FTE - SQL Server PFE
* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]
March 25, 2009 at 10:12 pm
Here are the links I had gotten...
http://go.microsoft.com/fwlink/?LinkId=111531&clcid=0x409
http://support.microsoft.com/?id=943345
http://technet.microsoft.com/en-us/library/cc262731.aspx
http://support.microsoft.com/kb/932744/
http://blogs.msdn.com/chrisfie/archive/2008/06/18/sharepoint-performance-tuning-references.aspx
Thanks.
Mohit.
Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
Microsoft FTE - SQL Server PFE
* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply