Stripe /full stripe size for RAID 10 for SQL 2012

what is the recommended stripe/full strip size for a Raid 10 configuration exclusively for SQL 2012 files which used for electronic  transaction authentication
shamnadAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ayoub RouziCeo & CoFounderCommented:
Below are the best practices
-      If you have the option of striping your firmware RAID then set it to 256k over 64k or 128k. You should opt for 256k because it helps to increase performance of SQL Server.
-      During the creation of the partitions, align partitions on (128sectors*512b sector) =64K track boundary. This will reduce the number of head movements caused by track spanning. It also reduces cache buffer allocations for trailing data that you may not access once it has been cached.
-      When you create the volume on each partition you need to do a full format and specify an Allocation unit (AU) Size of 64K on all volumes that will host your database files and an AU Size of 4K for volumes that will host your log files. Logs are read and written to differently than database files. Mostly all sequential and not page/extent driven. However, the track boundary alignment is not as important with an AU of 4k as it is with and AU of 64k it is still very important. With a 64k AU misaligned, you'll track span on each I/O as compared to track spanning on every 16th I/O with an AU of 4k.
-      Track boundary misalignment causes latency due to head movement but it also helps to over work your hard drives resulting if failure sooner rather than later.
-      You will see your most significant I/O gains during backups and restores.

Here is the commandline for Diskpart

C:\>diskpart
Microsoft DiskPart version 6.0.6001
Copyright (C) 1999-2007 Microsoft Corporation.
On computer: ASPIRINGGEEK

DISKPART> list disk
  Disk ###  Status      Size     Free     Dyn  GPT
  --------  ----------  -------  -------  ---  ---
  Disk 0    Online       186 GB      0 B
  Disk 1    Online       100 GB      0 B
  Disk 2    Online       120 GB      0 B
  Disk 3    Online       150 GB   150 GB

DISKPART> select disk 3
Disk 3 is now the selected disk.

DISKPART> create partition primary align=1024
DiskPart succeeded in creating the specified partition.

DISKPART> assign letter=F
DiskPart successfully assigned the drive letter or mount point.

DISKPART> format fs=ntfs unit=64K label="MyFastDisk" nowait

NTFS allocation unit sizes for large volumes
Link

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage

From novice to tech pro — start learning today.