New Windows 2008 Disk Partitioning Offset question - should I worry about it?

Ok - to make this clear...

If you are creating volumes on Windows Server 2008, you do not need to be concerned about the volume's partition offset because Windows Server 2008 will automatically set is to 1MB, which is a multiple of the common RAID stripe sizes and NTFS allocation unit sizes (both of which you should usually have set to 64K, unless you I/O subsystem won't let you go below 128K for the RAID stripe size - which is fine). In your question, you mention partition size, and what you're actually talking about is the NTFS allocation unit size (default 4K).

If you are installing a new Windows 2008 Server and then attaching volumes to it that were actually created using Windows Server 2003 or before, then unless you have previously used diskpart to change the partition offset from the default of 32.5K (63 x 512byte disk blocks), you must manually change it with diskpart, or recreate the volume.

My preference would be to backup your databases and then restore them on newly created volumes.

Hope this helps!

PS My blog post that you reference talks about having the correct partition offset, not partition size. And the whitepaper link in the first answer is the same one that I reference in the blog post you've already read.

It's how the partition is aligned on the physical disk (or raid lun). This is important because we want that alignment not to split a RAID stripe in the middle. Windows Server prior to 2008 aligned at a 32K boundary which worked fine on a single disk or a mirror pair but often split a stripe in the middle. To manually set partition alignment you must create the partition using the diskpart command line tool.

Here's some specific info for you:

Disk Partition Alignment Best Practices for SQL Server