Picking Allocation Size for NTFS
What is the right allocation size for NTFS with SQL Server and Hyper-V?
John Savill
March 23, 2014
1 Min Read
![Picking Allocation Size for NTFS Picking Allocation Size for NTFS](https://eu-images.contentstack.com/v3/assets/blt07f68461ccd75245/blt044f82e743bbb652/661cfa1edc83ea29b5f8679f/cables-multicolored-595x335_0_2.jpg?width=850&auto=webp&quality=95&format=jpg&disable=upscale)
Q: What allocation unit size should I use for my NTFS volume that will be running Hyper-V virtual machines (VMs) and SQL Server databases?
A: When formatting a partition, you can select an allocation unit size (cluster size) which has a default value (as documented at Microsoft Support). However, if you are running Hyper-V VMs or a SQL Server database, for best performance, set the allocation unit size to 64K.
This can only be set when the volume is formatted, so if you have a smaller value, you would need to move the data, then perform a fresh format. To check the cluster size, use fsutil and look at the Bytes Per Cluster value:
C:>fsutil fsinfo ntfsinfo c:NTFS Volume Serial Number : 0xd40efd830efd5f44NTFS Version : 3.1LFS Version : 2.0Number Sectors : 0x000000000945f7ffTotal Clusters : 0x000000000128beffFree Clusters : 0x0000000000b942e8Total Reserved : 0x0000000000000a40Bytes Per Sector : 512Bytes Per Physical Sector : 512Bytes Per Cluster : 4096Bytes Per FileRecord Segment : 1024Clusters Per FileRecord Segment : 0Mft Valid Data Length : 0x000000000b5c0000Mft Start Lcn : 0x00000000000c0000Mft2 Start Lcn : 0x0000000000000002Mft Zone Start : 0x00000000000cb5c0Mft Zone End : 0x00000000000cc820Resource Manager Identifier : 1CDFE057-1264-11E2-B782-C689895D03AC
About the Author(s)
Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.
You May Also Like