disk alignment partitioning for SQL performance

KevinK recommends for SQL on Windows Server 2003  to have 64K sector offset for the Data drives.


Ours has 32K as the Starting Offset. Since 64K is multiples of 32K, will that be ok, or is it recommended to change it to 64KB.

Who is Participating?
I know that it is recommended to have 64K, but after realigning disk and setting to 64K - did not gain any performance (tested with SQL backup to see MB/s) and users reported no difference. Our ERP DB is ~20GB.
By the way, Windows 2008 Server sets 64K by default.
anushahannaAuthor Commented:
Ours is 122GB.

Vaidas911, did you do it on W 2003 Server?

I thought ours was 32KB, but the it is only 31.5K of metadata.
Ours also W 2003 Server, and yes, 31.5K is standart.
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

What would make a monster of a difference is increasing your RAID controller's stripe size and getting more cache to your controller, adding battery to have a battery backed cache.. That surely makes things better.

If it's not possible, then it's a good idea to span the data on more spindles, specially on your case with such a huge database.
anushahannaAuthor Commented:
tiago_aviz, it is just not about the stripe size, but  if it will lead to 2 IO ops instead of 1.

We have 100 spindles underneath our LAN, but still the Disk IO has remained the same..
anushahannaAuthor Commented:
Vaidas911, perhaps you should have gone higher than 64k?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.