{"id":1130,"date":"2026-11-13T23:10:54","date_gmt":"2026-11-13T23:10:54","guid":{"rendered":"https:\/\/windows-vps.org\/blog\/?p=1130"},"modified":"2026-11-13T23:10:54","modified_gmt":"2026-11-13T23:10:54","slug":"ntfs-allocation-unit-size-sql-server-windows-vps","status":"publish","type":"post","link":"https:\/\/windows-vps.org\/blog\/ntfs-allocation-unit-size-sql-server-windows-vps\/","title":{"rendered":"NTFS Allocation Unit Size for SQL Server on a Windows VPS: 64 KB Clusters and Alignment"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Allocation unit size is chosen once, at format time, and then silently affects every read and write for the life of the volume. On a Windows VPS running SQL Server, the default 4 KB NTFS cluster forces most database I\/O into read-modify-write operations that trickle across multiple clusters \u2014 and on network-backed or thin-provisioned virtual disks that is measurable. This guide covers the cluster sizes that matter, the 64 KB SQL Server sweet spot, its interaction with physical sector and VMFS\/block-storage geometry, and how to fix an existing volume without reinstalling.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What Allocation Unit Size Actually Controls<\/h2>\n\n\n<p class=\"wp-block-paragraph\">NTFS divides the volume into clusters (&#8220;allocation units&#8221;) and allocates file space in whole clusters. A 4 KB cluster means a 60 KB SQL Server read is served by 15 separate cluster reads; a 64 KB cluster means one. The difference is not about wasting space for small files \u2014 SQL data files are huge and sequential \u2014 it is about how many distinct I\/O operations the filesystem and the virtual disk have to perform per logical request, and how many page fragments the storage layer must reassemble.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">ReFS behaves differently: it uses a fixed 64 KB block and cannot be formatted with another allocation unit size through the Format dialog, which is one reason DB volumes usually stay on NTFS.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Recommended Sizes by Workload<\/h2>\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Workload<\/th><th>File system<\/th><th>Allocation unit<\/th><th>Rationale<\/th><\/tr><\/thead><tbody><tr><td>SQL Server data (.mdf\/.ndf)<\/td><td>NTFS<\/td><td>64 KB<\/td><td>Matches SQL Server&#8217;s 64 KB extent; one extent read = one cluster<\/td><\/tr><tr><td>SQL Server log (.ldf)<\/td><td>NTFS<\/td><td>64 KB<\/td><td>Sequential writes; fewer clusters per log flush<\/td><\/tr><tr><td>SQL Server backup target<\/td><td>NTFS<\/td><td>64 KB<\/td><td>Streaming sequential I\/O; also better for compression<\/td><\/tr><tr><td>IIS content root (wwwroot)<\/td><td>NTFS<\/td><td>4 KB (default)<\/td><td>Many small files; large clusters waste space<\/td><\/tr><tr><td>Windows system volume (C:)<\/td><td>NTFS<\/td><td>4 KB (default)<\/td><td>Never change this; updates and WinSxS assume it<\/td><\/tr><tr><td>Backup\/archive volumes with large files<\/td><td>NTFS<\/td><td>64 KB<\/td><td>Fewer metadata updates per GB<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The rule of thumb: 64 KB for anything dominated by large sequential or extent-aligned I\/O, 4 KB for volumes that hold tens of thousands of small files. A single volume holding both is a compromise; on anything larger than a few hundred GB, split the database files onto their own VHDX with 64 KB clusters.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Aligning With the Virtual Disk and Physical Sector<\/h2>\n\n\n<p class=\"wp-block-paragraph\">The cluster size only helps if it lands on an aligned boundary of the underlying storage. NTFS formats created on Windows Server 2012 and later are 1 MB-aligned by default, which is correct for virtually all modern virtual disks. Verify rather than assume:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Physical sector size and logical sector size of the disk\nGet-Disk | Format-Table Number,FriendlyName,PartitionStyle,BusType,LogicalSectorSize,PhysicalSectorSize\n\n# Allocation unit size per volume\nGet-Volume | Format-Table DriveLetter,FileSystem,AllocationUnitSize,SizeRemaining\n\n# Free space and cluster count sanity check\nfsutil fsinfo ntfsinfo D:<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">On a VPS, <em>PhysicalSectorSize<\/em> is often reported as 4096 even when the backing storage uses 512e emulation. A 64 KB cluster is an integer multiple of every one of these, so there is little to tune. What matters is avoiding a volume offset of, say, 32 KB against a 64 KB stripe \u2014 which happens when a partition was created by an old tool.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Formatting a New Data Volume Correctly<\/h2>\n\n\n<p class=\"wp-block-paragraph\">Attach the VHDX or second data disk, initialise it as GPT, then format with an explicit allocation unit size. Do not use the Format dialog&#8217;s default and then try to fix it later:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Initialise and format a new data disk as 64 KB NTFS\nInitialize-Disk -Number 1 -PartitionStyle GPT\nNew-Partition -DiskNumber 1 -UseMaximumSize -DriveLetter D\nFormat-Volume -DriveLetter D -FileSystem NTFS -AllocationUnitSize 65536 `\n  -NewFileSystemLabel 'SQLData' -Confirm:$false\n\n# Confirm the result\nGet-Volume -DriveLetter D | Format-List DriveLetter,FileSystem,AllocationUnitSize<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For an existing volume, <em>Format-Volume<\/em> with <em>-AllocationUnitSize<\/em> will refuse to reformat without confirmation. If the volume holds data, the only safe conversion path is a new volume plus a file copy. That is the usual reason this decision should be made when the VPS is provisioned, not after launch. The <a href=\"https:\/\/windows-vps.org\/\">Windows VPS hosting plans and specifications<\/a> page is where you size the data disk before the first boot.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Converting an Existing Volume Without Reinstalling Windows<\/h2>\n\n\n<p class=\"wp-block-paragraph\">There is no supported in-place command to change NTFS allocation unit size \u2014 <em>fsutil<\/em>, <em>chkdsk<\/em>, and <em>defrag<\/em> will not do it. The practical procedure on a VPS is a second data disk and a cutover:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Attach a new virtual disk of equivalent or larger size and format it with 64 KB clusters.<\/li>\n<li>Put the database in read-only, or better, stop the SQL Server service to guarantee a consistent copy.<\/li>\n<li>Copy with <em>robocopy \/MIR \/COPYALL \/J<\/em> to preserve ACLs and use unbuffered I\/O.<\/li>\n<li>Detach the old volume or rename it, then mount the new one at the original drive letter.<\/li>\n<li>Start SQL Server, run <em>DBCC CHECKDB<\/em>, and take a fresh full backup before reopening to clients.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Expect 20\u201360 minutes of downtime for a mid-sized database. Schedule the cutover; do not improvise it during business hours.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">When 64 KB Hurts: The Counter-Arguments<\/h2>\n\n\n<p class=\"wp-block-paragraph\">Large clusters are not free. A 64 KB cluster means a 1 KB file consumes 64 KB, so a volume full of small files \u2014 a multi-million-file log directory or a git working tree \u2014 can lose 20\u201340% of its capacity to slack space. In those cases, use the default 4 KB and accept the extra clusters per I\/O. Also note that Windows Server deduplication on NTFS requires the volume to use 4 KB clusters; if you rely on dedup for a file server role, you cannot adopt 64 KB there.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">SQL Server does not care about slack because its files are pre-allocated and large, but it does care about the instant file initialisation setting and the 64 KB extent size \u2014 which is exactly why the alignment matters. A 64 KB cluster that is misaligned with the underlying storage can be worse than a well-aligned 4 KB cluster, so verify with the commands above before assuming the bigger number is better.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Verifying the Gain Instead of Trusting the Theory<\/h2>\n\n\n<p class=\"wp-block-paragraph\">Measure before and after with <em>\\PhysicalDisk(*)\\Avg. Disk sec\/Transfer<\/em> and SQL Server&#8217;s own <em>\\SQLServer:Databases(*)\\Log Write Waits<\/em>. On a spinning-backed virtual disk the gain is usually visible as lower average transfer latency; on NVMe it may be within noise, because the device&#8217;s own queue depth hides cluster-count differences. The right conclusion is the measured one, not the textbook one \u2014 and on a small VPS, the config effort should follow the bottleneck. If I\/O latency remains high after correct alignment, the constraint is the host&#8217;s storage tier, and the entry-level options compared on the <a href=\"https:\/\/windows-vps.org\/\">Windows VPS hosting plans and specifications<\/a> page explain which tiers provide NVMe-backed volumes.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Allocation unit size is chosen once, at format time, and then silently affects every read and write for the life of the volume. On a Windows VPS running SQL Server, the default 4 KB NTFS cluster forces most database I\/O into read-modify-write operations that trickle across multiple clusters \u2014 and on network-backed or thin-provisioned virtual &#8230; <a title=\"NTFS Allocation Unit Size for SQL Server on a Windows VPS: 64 KB Clusters and Alignment\" class=\"read-more\" href=\"https:\/\/windows-vps.org\/blog\/ntfs-allocation-unit-size-sql-server-windows-vps\/\" aria-label=\"Read more about NTFS Allocation Unit Size for SQL Server on a Windows VPS: 64 KB Clusters and Alignment\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":0,"footnotes":""},"categories":[9,5],"tags":[],"class_list":["post-1130","post","type-post","status-publish","format-standard","hentry","category-hosting-workflows","category-tutorials-guides"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v26.1 (Yoast SEO v26.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>NTFS Allocation Unit Size for SQL Server on a Windows VPS: 64 KB Clusters and Alignment - Windows VPS Blog<\/title>\n<meta name=\"description\" content=\"Allocation unit size is chosen once, at format time, and then silently affects every read and write for the life of the volume. On a Windows VPS running\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/windows-vps.org\/blog\/ntfs-allocation-unit-size-sql-server-windows-vps\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"NTFS Allocation Unit Size for SQL Server on a Windows VPS: 64 KB Clusters and Alignment\" \/>\n<meta property=\"og:description\" content=\"NTFS Allocation Unit Size for SQL Server on a Windows VPS: 64 KB Clusters and Alignment\" \/>\n<meta property=\"og:url\" content=\"https:\/\/windows-vps.org\/blog\/ntfs-allocation-unit-size-sql-server-windows-vps\/\" \/>\n<meta property=\"og:site_name\" content=\"Windows VPS Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-13T23:10:54+00:00\" \/>\n<meta name=\"author\" content=\"windows-vps\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@myxiechengxuan\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"windows-vps\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/windows-vps.org\/blog\/ntfs-allocation-unit-size-sql-server-windows-vps\/\",\"url\":\"https:\/\/windows-vps.org\/blog\/ntfs-allocation-unit-size-sql-server-windows-vps\/\",\"name\":\"NTFS Allocation Unit Size for SQL Server on a Windows VPS: 64 KB Clusters and Alignment - Windows VPS Blog\",\"isPartOf\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/#website\"},\"datePublished\":\"2026-11-13T23:10:54+00:00\",\"author\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58\"},\"description\":\"Allocation unit size is chosen once, at format time, and then silently affects every read and write for the life of the volume. On a Windows VPS running\",\"breadcrumb\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/ntfs-allocation-unit-size-sql-server-windows-vps\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/windows-vps.org\/blog\/ntfs-allocation-unit-size-sql-server-windows-vps\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/windows-vps.org\/blog\/ntfs-allocation-unit-size-sql-server-windows-vps\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/windows-vps.org\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"NTFS Allocation Unit Size for SQL Server on a Windows VPS: 64 KB Clusters and Alignment\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#website\",\"url\":\"https:\/\/windows-vps.org\/blog\/\",\"name\":\"Windows VPS Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/windows-vps.org\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58\",\"name\":\"windows-vps\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g\",\"caption\":\"windows-vps\"},\"sameAs\":[\"https:\/\/windows-vps.org\/blog\",\"https:\/\/x.com\/myxiechengxuan\"],\"url\":\"https:\/\/windows-vps.org\/blog\/author\/myxiechengxuan\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"NTFS Allocation Unit Size for SQL Server on a Windows VPS: 64 KB Clusters and Alignment - Windows VPS Blog","description":"Allocation unit size is chosen once, at format time, and then silently affects every read and write for the life of the volume. On a Windows VPS running","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/windows-vps.org\/blog\/ntfs-allocation-unit-size-sql-server-windows-vps\/","og_locale":"en_US","og_type":"article","og_title":"NTFS Allocation Unit Size for SQL Server on a Windows VPS: 64 KB Clusters and Alignment","og_description":"NTFS Allocation Unit Size for SQL Server on a Windows VPS: 64 KB Clusters and Alignment","og_url":"https:\/\/windows-vps.org\/blog\/ntfs-allocation-unit-size-sql-server-windows-vps\/","og_site_name":"Windows VPS Blog","article_published_time":"2026-11-13T23:10:54+00:00","author":"windows-vps","twitter_card":"summary_large_image","twitter_creator":"@myxiechengxuan","twitter_misc":{"Written by":"windows-vps","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/windows-vps.org\/blog\/ntfs-allocation-unit-size-sql-server-windows-vps\/","url":"https:\/\/windows-vps.org\/blog\/ntfs-allocation-unit-size-sql-server-windows-vps\/","name":"NTFS Allocation Unit Size for SQL Server on a Windows VPS: 64 KB Clusters and Alignment - Windows VPS Blog","isPartOf":{"@id":"https:\/\/windows-vps.org\/blog\/#website"},"datePublished":"2026-11-13T23:10:54+00:00","author":{"@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58"},"description":"Allocation unit size is chosen once, at format time, and then silently affects every read and write for the life of the volume. On a Windows VPS running","breadcrumb":{"@id":"https:\/\/windows-vps.org\/blog\/ntfs-allocation-unit-size-sql-server-windows-vps\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/windows-vps.org\/blog\/ntfs-allocation-unit-size-sql-server-windows-vps\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/windows-vps.org\/blog\/ntfs-allocation-unit-size-sql-server-windows-vps\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/windows-vps.org\/blog\/"},{"@type":"ListItem","position":2,"name":"NTFS Allocation Unit Size for SQL Server on a Windows VPS: 64 KB Clusters and Alignment"}]},{"@type":"WebSite","@id":"https:\/\/windows-vps.org\/blog\/#website","url":"https:\/\/windows-vps.org\/blog\/","name":"Windows VPS Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/windows-vps.org\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58","name":"windows-vps","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g","caption":"windows-vps"},"sameAs":["https:\/\/windows-vps.org\/blog","https:\/\/x.com\/myxiechengxuan"],"url":"https:\/\/windows-vps.org\/blog\/author\/myxiechengxuan\/"}]}},"_links":{"self":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/1130","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/comments?post=1130"}],"version-history":[{"count":1,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/1130\/revisions"}],"predecessor-version":[{"id":1133,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/1130\/revisions\/1133"}],"wp:attachment":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/media?parent=1130"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/categories?post=1130"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/tags?post=1130"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}