Blog Post
Announcing Native NVMe in Windows Server 2025: Ushering in a New Era of Storage Performance
This feature counteracts the SQL Server sector size workaround for NVMe drives making it so that SQL Server will no longer run: "HKLM\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device" /v "ForcedPhysicalSectorSizeInBytes". How are we to see a benefit on SQL Database servers if we can't run SQL server on NVMe drives?
I found this article on this topic: https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/database-file-operations/troubleshoot-os-4kb-disk-sector-size?tabs=registry-editor
However, it does seem like something that any NVMe firmware would already resolve on its own. Sector sizes rarely align perfectly and drives these days are usually designed to optimize themselves without a lot of customization, as long as a reasonable sector size is chosen. Back in the old days, companies like Oracle would not certify NAND drives for use with tools like Hyperion EPM and its various databases. These days, I don't think they do that anymore.