Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
jhender31
Starting Member
1 Post |
Posted - 2006-12-18 : 13:27:48
|
One of our SQL servers has an interesting disk configuration. I am wondering if the community can provide me some feedback. The server has the data broken down and placed among many different logical drives, 19 to be exact. Each drive letter is made up of a pair of 15k scsi drives mirrored using HP RAID utility. Our main database on this server has the filegroups and ndf files all on thier own hard drives, which are mirrored. The performance of the server is good. We never recieve complaints about it. The DBA who created this server left the company so I cannot ask him about it. Can I please have any and all comments regarding this? I can add more details as necessary. Thank You all in advance. |
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2006-12-19 : 14:52:35
|
Well, that is an insteresting disk config. It probably not a bad config, but I do see one weakness with it. If you have one table / index that gets hit hard, it's only going to be accessed as fast as the one disk that it's on. Now, if you had all the disks in one larger (or possibly 2-3) array, then you could read that table much more quickly since you'd be reading for several disks.I probably would move away from 19 separate RAID 1 arrays and move to several RAID 5 or RAID 0/1 arrays. The reason I say this is because most OLTP databases are about 60-70% read and 30-40% write. That being said, you should optimise your disk config for read performance. That points towards a RAID 5 which has GREAT read performance, but poor write performance or towards RAID 0/1 that has a good balance of read vs write.Hope that helps!Michael<Yoda>Use the Search page you must. Find the answer you will. Cursors, path to the Dark Side they are. Avoid them, you must. Use Order By NewID() to get a random record you will.</Yoda>Opinions expressed in this post are not necessarily those of TeleVox Software, inc. All information is provided "AS IS" with no warranties and confers no rights. |
 |
|
|
|
|
|
|