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 |
|
shifty1981
Starting Member
20 Posts |
 Posted - 2011-01-27 : 11:35:03
|
| I've read many articles recommending 64K stripe size along with 64K allocation size when formatting the volume in Windows. I have a couple of questions: 1. The document below recommends 256K stripe size in some scenarios. How do I determine if that pertains to us? Our databases are around 500GB in size and the data only stays in the DB for about 2 weeks before it is gone. We have high IO tables on their own RAID10 sets and the tempdb and transaction logs on RAID1 sets. The OS and pagefile are on a RAID1 set. These are all 6Gbps internal SCSI drives with a 512 or 1024MB cache battery backed up raid controller from DELL.http://download.microsoft.com/download/4/7/a/47a548b9-249e-484c-abd7-29f31282b04d/PhysDBStor.doc2. The 64K and 64K recommendation almost always seems to be talking about the database volume. Is the stripe and allocation size recommendation the same for:a. transaction log volumeb. tempdb volumec. os/page file volume? 3. our servers receive data from clients that average around 150K in size (and won't exceed 300K). Our database stores info about that data and then we store the data itself on an iSCSI SAN volume we present to the server. How should the stripe size and allocation size differ for that volume? Typically it's a RAID10 volume on 14 drives with 2 hotspares. Our environment is Windows Server 2008 R2 x64 Enteprise; SQL Server 2008 R2 Enterprise; |
|
|
|
|
|
SQL Server Drive stripe and allocation size