Azure migrate changed disk physical sector size

Joe Correia 1 Reputation point
2022-10-10T15:21:26.797+00:00

Used Azure Migrate to migrate a SQL Server to Azure.
The on-premise SQL server has 2 disks (C: and E:) each having 512 bytes per sector and 512 bytes per Physical Sector settings.
Post migration the SQL Server C: disk now show 512 bytes per sector and 4096 bytes per Physical Sector settings and the E: (LOG) drive shows 512 bytes per sector and 512 bytes per physical sector.

This is causing SQL to throw errors misaligned log IOs.

Is there no way to deploy a disk to the SQL VM and set the sectors back to 512 bytes per physical sector?

Have already reviewed this: https://support.microsoft.com/en-us/topic/kb3009974-fix-slow-synchronization-when-disks-have-different-sector-sizes-for-primary-and-secondary-replica-log-files-in-sql-server-ag-and-logshipping-environments-ed181bf3-ce80-b6d0-f268-34135711043c

Azure Migrate
Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
723 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Luke Murray 10,611 Reputation points MVP
    2022-10-10T18:50:10.623+00:00

    I believe Ultra disks are the only disks available for 512 sector sizes: https://learn.microsoft.com/en-us/azure/virtual-machines/disks-types?WT.mc_id=AZ-MVP-5004796#:~:text=Ultra%20disks%20support%20a,sector%20size%20is%20required.

    You should have to create a new disk and deploy the database to that drive.

    0 comments No comments