I'm setting up a new SQL Server 2008 r2 in AWS with IO1 SSD EBS volumes. My smaller EBS volumes are aligned correctly when they were formatted but the larger volumes, 3TB, are not because they used GPT instead of MBR.

I'm going though the setup check list in Brent Ozar's First Responder Kit and referencing another post that is asking generally about SSDs as well a document from AWS to ensure I have it optimized however I'm not finding anything of relevance when it comes to disk partition alignments for GPT or if it's necessary to do for IO1 SSD EBS Volumes in AWS.

Is partition alignment needed when it comes to AWS' SSD EBS volumes? Is there a best practice for what the alignment should be for GPT formatted volumes?

  • I stopped at “a new SQL Server 2008 R2” - why on earth is this no longer even remotely supported version the one you’re choosing in August 2019? – Aaron Bertrand Aug 6 '19 at 21:34
  • @AaronBertrand Money for licensing – Aaron Aug 6 '19 at 22:06
  • Where are you buying a valid 2008 R2 license today? – Aaron Bertrand Aug 6 '19 at 22:07
  • @AaronBertrand we have mobility on our existing per socket licensing – Aaron Aug 6 '19 at 22:13
  • Trust me I’m not happy about having to stay on it either. Besides the out of support it’s becoming harder to find the .net framework installations needed – Aaron Aug 6 '19 at 22:19

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.